Site seems really slow today

D'oh.  After some back and forth, it appears the datacenter erroneously set the backup time to 4PM EST (1PM PST), which corresponds to this slowdown.  I've had them change it to 4AM EST, which was the intended time to begin with.  Anyways, let me know if the problem is solved after todays "window".  Thanks.

-Allen

Is it just me or does NCKA slow to a crawl on occasions during the day? Backup running?

He shoots, he scores! 

Well, eventually I got it right.  Err, I think I got it right.  Was there no slowdown today?

Thanks for all of your help Krusty!

-Allen

I missed the window today. I will let you know if I run into it again.

I'll do that tomorrow Allen.  I've also noticed a big slow down around 1/1:30PM.  Figured it was backups or something.  Not sure why it would be bandwidth related for me.  I'm sitting ON a internet backbone 

I'm not sure why I never noticed it, or why Google Analytics didn't either.  Perhaps I have some super admin performance privileges?

-Allen

What? Did I get any kinda credit for that Allen. I sent you that message about the posts Being ahead of time on my tablet.?? Something , Nothing ?   .

Alex

You're getting ahead of yourself ...   

-Allen

A shot in the dark. i am sure this is on a much smaller scale. But i have found guys who have checked there clock or calendar on there computers here at work and accidently changed them. And found that it had locked them out of some sites or other complications. I was close. 

What? Did I get any kinda credit for that Allen. I sent you that message about the posts Being ahead of time on my tablet.?? Something , Nothing ?   .

Alex

You're getting ahead of yourself ...   

-Allen

A shot in the dark. i am sure this is on a much smaller scale. But i have found guys who have checked there clock or calendar on there computers here at work and accidently changed them. And found that it had locked them out of some sites or other complications. I was close. 

Changing your clock on the computer doesn't mean you get off work any sooner!

What? Did I get any kinda credit for that Allen. I sent you that message about the posts Being ahead of time on my tablet.?? Something , Nothing ?   .

Alex

You're getting ahead of yourself ...   

-Allen

A shot in the dark. i am sure this is on a much smaller scale. But i have found guys who have checked there clock or calendar on there computers here at work and accidently changed them. And found that it had locked them out of some sites or other complications. I was close. 

Changing your clock on the computer doesn't mean you get off work any sooner!

 

So you are saying Allen was trying to get off work early ??

Alex

So you are saying Allen was trying to get off work early ??

Alex

Just 12 hours early

I think you fixed it. I was up late and tried to load a page about 1:12am and it was 1:43am before I could get a page to load. Problem solved!

I think you fixed it. I was up late and tried to load a page about 1:12am and it was 1:43am before I could get a page to load. Problem solved!

I don't consider it fixed.  The problem is just pushed around.

I'm also still not sure why you can't get a page to load during this time.  I find it very strange that performance is user specific.  I still haven't really seen significant slowdown myself.  Yet you and some others see it consistently.

I'm also investigating a server upgrade that will alleviate backup penalties.

-Allen

Seemed slow again a minute ago...

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\>ping ncka.org

Pinging ncka.org [184.168.221.29] with 32 bytes of data:
Reply from 184.168.221.29: bytes=32 time=25ms TTL=54
Reply from 184.168.221.29: bytes=32 time=34ms TTL=54
Request timed out.
Request timed out.

Ping statistics for 184.168.221.29:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
    Minimum = 25ms, Maximum = 34ms, Average = 29ms

Eh, may be my connection:


Pinging ncka.org [184.168.221.29] with 32 bytes of data:
Reply from 184.168.221.29: bytes=32 time=25ms TTL=54
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 184.168.221.29:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
    Minimum = 25ms, Maximum = 25ms, Average = 25ms

C:\Users\asatre>tracert ncka.org

Tracing route to ncka.org [184.168.221.29]
over a maximum of 30 hops:

  1     *        8 ms     4 ms  192.168.60.1
  2     *        5 ms     3 ms  future-208-85-42-1.pandora.com [208.85.42.1]
  3    12 ms     7 ms     4 ms  ae14.mpr4.sjc7.us.zip.zayo.com [128.177.170.53]

  4     *        *        6 ms  be6461.ccr21.sjc03.atlas.cogentco.com [154.54.10
.193]
  5    12 ms     7 ms     6 ms  be2000.ccr21.sjc01.atlas.cogentco.com [154.54.6.
105]
  6     *       16 ms    15 ms  be2160.ccr21.lax01.atlas.cogentco.com [154.54.27
.161]
  7    19 ms    15 ms    19 ms  be2180.ccr23.lax05.atlas.cogentco.com [154.54.41
.58]
  8    16 ms    15 ms    15 ms  38.104.84.90
  9     *        *        *     Request timed out.
 10    26 ms    32 ms    25 ms  ip-184-168-0-86.ip.secureserver.net [184.168.0.8
6]
 11    30 ms    26 ms    26 ms  te0-0-0-7.trmc0215-01.ars.mgmt.phx3.gdg [184.168
.0.85]
 12    26 ms    25 ms    40 ms  ip-184-168-0-102.ip.secureserver.net [184.168.0.
102]
 13    25 ms    25 ms    25 ms  ip-184-168-221-29.ip.secureserver.net [184.168.2
21.29]

Trace complete.

Well... still one hop that didn't look good:


Pinging ncka.org [184.168.221.29] with 32 bytes of data:
Reply from 184.168.221.29: bytes=32 time=25ms TTL=54
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 184.168.221.29:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
    Minimum = 25ms, Maximum = 25ms, Average = 25ms

C:\Users\asatre>tracert ncka.org

Tracing route to ncka.org [184.168.221.29]
over a maximum of 30 hops:

  1     *        8 ms     4 ms  192.168.60.1
  2     *        5 ms     3 ms  future-208-85-42-1.pandora.com [208.85.42.1]
  3    12 ms     7 ms     4 ms  ae14.mpr4.sjc7.us.zip.zayo.com [128.177.170.53]

  4     *        *        6 ms  be6461.ccr21.sjc03.atlas.cogentco.com [154.54.10
.193]
  5    12 ms     7 ms     6 ms  be2000.ccr21.sjc01.atlas.cogentco.com [154.54.6.
105]
  6     *       16 ms    15 ms  be2160.ccr21.lax01.atlas.cogentco.com [154.54.27
.161]
  7    19 ms    15 ms    19 ms  be2180.ccr23.lax05.atlas.cogentco.com [154.54.41
.58]
  8    16 ms    15 ms    15 ms  38.104.84.90
  9     *        *        *     Request timed out.
 10    26 ms    32 ms    25 ms  ip-184-168-0-86.ip.secureserver.net [184.168.0.8
6]
 11    30 ms    26 ms    26 ms  te0-0-0-7.trmc0215-01.ars.mgmt.phx3.gdg [184.168
.0.85]
 12    26 ms    25 ms    40 ms  ip-184-168-0-102.ip.secureserver.net [184.168.0.
102]
 13    25 ms    25 ms    25 ms  ip-184-168-221-29.ip.secureserver.net [184.168.2
21.29]

Trace complete.

And pings are still showing some loss:

C:\Users\asatre>ping ncka.org

Pinging ncka.org [184.168.221.29] with 32 bytes of data:
Reply from 184.168.221.29: bytes=32 time=71ms TTL=55
Reply from 184.168.221.29: bytes=32 time=70ms TTL=55
Reply from 184.168.221.29: bytes=32 time=78ms TTL=55
Request timed out.

Ping statistics for 184.168.221.29:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 70ms, Maximum = 78ms, Average = 73ms

Should have said that I've switched networks between the tests, so don't believe that it's my connection causing packet loss.