Slow path to neon

[Ron]

Has anyone else been seeing really slow response times over the last day/week?

last 24 hours:

Last 7 days:


Yes, I've opened a ticket (only 20 minutes ago).

Even the "lower bumps" are response times >3 seconds, which really isn't very acceptable. That means that over the last 24 hourse, my site has seen 25% unacceptable response times.

[Ron]

27 minutes -- just received a response that they will look into it and update me as soon as possible. Cool.

[Orbitz]

Hi Ron,

Where and How you get this info? Could you tell me please!

yah, I am new here and I like the support here so far - The support team responds to us very quickly and do their jobs effectively.

cheers!

[Ron]

Orbitz, I sent you a PM

[Ron]

Well, no update, and the site's been slow off and on all day...



Can't someone look at this stuff proactively? Can't they run a watchdog program - like I do- and have it email when there's a major delay?

Did the pictures serve up fast for you?

[JPC-Les]

Hi Ron,
I have asked a tech to look into this just to be sure. Is it possible you can run some traceroutes to the server when you incur the delays to see where the slowdown occurs?

are these results produced from your physical location or a 3rd party watchdog service?

[Ron]

Both... These reports are from the watchdog service... Which I check when things are running poorly.

The ticket has a traceroute that I took when I posted earlier... It timed out adjacent to cyrusone

Here's the tracert that I ran, minus the first few identifying hops.

8 38 ms 55 ms 39 ms tbr2-cl5.cgcil.ip.att.net [12.122.10.106]
9 47 ms 45 ms 46 ms tbr2-cl7.sl9mo.ip.att.net [12.122.10.46]
10 59 ms 59 ms 60 ms tbr2-cl6.dlstx.ip.att.net [12.122.10.90]
11 64 ms 62 ms 60 ms tbr1-p013601.dlstx.ip.att.net [12.122.9.161]
12 62 ms 63 ms 65 ms tbr2-cl1.hs1tx.ip.att.net [12.122.10.130]
13 63 ms 65 ms 64 ms gbr1-p40.hs1tx.ip.att.net [12.122.12.146]
14 61 ms 62 ms 61 ms gar1-p360.hs1tx.ip.att.net [12.123.134.21]
15 * * * Request timed out.
16 98 ms 64 ms 64 ms 69-7-175-35.cyrusone.com [69.7.175.35]
17 * 62 ms 65 ms 69-7-160-227.cyrusone.com [69.7.160.227]
18 66 ms 66 ms 65 ms 69.73.164.105

Thanks!

[Vin DSL]

Originally posted by Ron
Has anyone else been seeing really slow response times over the last day/week?

Yeah, but it doesn't have anything to do with Neon. Neutron has been doing the same thing.

Your timeline is correct. I've noticed it for anywhere from a few days to the last week.

Those monitoring services are okay, but they obviously don't indicate anything meaningful, e.g. don't pinpoint the problem. And, they are usually inaccurate themselves.

What I have noticed, when this happens (through personal observation), is my page generation times are spiking. That would indicate a problem with MySQL.

Put another way, instead of it taking 0.4 sec. to generate a page, it's taking 15-20 sec. to generate.

I would suggest that your 'watchdog' is barking up the wrong tree...

[Vin DSL]

Oh, BTW, for what it's worth, when this has happened on my site, I have been doing an 'uptime' and server load has been normal every time. I'll check the sql server for slow queries, and whatever, next time...

[Ron]

This watchdog simply attempts to download a simple html web page, not mySQL.

I have another set up to access a page that relies on mySQL.

http://www.oes.org/html/a_page_for_master_com.html

Woof

[Vin DSL]

LoL! Guess I can forget that...

This MySQL server has been running for 31 days, 7 hours, 50 minutes and 50 seconds.
It started up on Feb 24, 2004 at 02:35 PM.

Query statistics: Since its startup, 24,375,347 queries have been sent to the server.

Slow launch threads: 0 
Slow queries: 9

You got that server smokin', JagPC!!!

[Vin DSL]

Hrm... that begs the question... Server load is okay, MySQL is smokin, so where's the holdup? PHP?

[Vin DSL]

Nope, that can't be right...

Okay, anyway, it comes and goes. I think that's the key...

[JPC-Les]

Originally posted by Ron
Both... These reports are from the watchdog service... Which I check when things are running poorly.

The ticket has a traceroute that I took when I posted earlier... It timed out adjacent to cyrusone

Here's the tracert that I ran, minus the first few identifying hops.

8 38 ms 55 ms 39 ms tbr2-cl5.cgcil.ip.att.net [12.122.10.106]
9 47 ms 45 ms 46 ms tbr2-cl7.sl9mo.ip.att.net [12.122.10.46]
10 59 ms 59 ms 60 ms tbr2-cl6.dlstx.ip.att.net [12.122.10.90]
11 64 ms 62 ms 60 ms tbr1-p013601.dlstx.ip.att.net [12.122.9.161]
12 62 ms 63 ms 65 ms tbr2-cl1.hs1tx.ip.att.net [12.122.10.130]
13 63 ms 65 ms 64 ms gbr1-p40.hs1tx.ip.att.net [12.122.12.146]
14 61 ms 62 ms 61 ms gar1-p360.hs1tx.ip.att.net [12.123.134.21]
15 * * * Request timed out.
16 98 ms 64 ms 64 ms 69-7-175-35.cyrusone.com [69.7.175.35]
17 * 62 ms 65 ms 69-7-160-227.cyrusone.com [69.7.160.227]
18 66 ms 66 ms 65 ms 69.73.164.105

Thanks!

Is this taken during slow response times?

[voogru]

Only slightly related, I havent noticed any "slowdowns" on neon (but I'm not really paying much attention to the speed), but rather I'm having problems accessing my site from one of my servers.

I can view my site fine at home and other people can also view it just fine, but not from my server (You'll need to see my thread on it for more details).

The catch is, its only happening on neon. I havent had any access problems on any other machines (pinging/traceroutes) all come out fine.