How can I check the reason for the delay and timeout of an HTTP request?

I issue a simple GET request to my server and it comes back after ~ 1.2 seconds (using Firebug NET tab, the "wait for a response" part - not even the full response time)

My ping to the server is 0.250

Using a Passenger with rails 2.3.3, in the rails log request takes ~ 0.023

My server is included in GoDaddy, so I also checked my home page with firebug - their page timeout is ~ 0.320

Worst case should be around 0.4 ... so where did I lose the other 0.8 seconds?

What else can I check?

Edit:

It looks like it is not rails related - Image request (which only apache responds, doest hits rails at all) takes ~ 1.2 seconds also

+2


source to share


4 answers


Try setting PassengerPoolIdleTime to 0 in your servers or VHosts settings. Perhaps your server is shutting down your application instances for quick start and starting a new instance with each request, which usually takes quite a long time.



Take a look at the documentation for more information on this setting: http://modrails.com/documentation/Users%20guide%20Apache.html#PassengerPoolIdleTime

0


source


GoDaddy can have a reverse proxy between you and your HTTP server.

They might do something like send you response headers right away, and then maybe serve you the response content from the cache.



So, from the point of view of your HTTP server, the response is being transmitted. It then goes to GoDaddy's reverse proxy and then finally to your web browser.

+1


source


If your files are hosted for GoDaddy, this is not the same as being hosted on the home page.

Have you checked other pages hosted on the same server? Possibly due to database connections or "slow" connections such as this, which could cause the page to take a while before it is sent back to the client.

0


source


It doesn't look like this is your problem, but with the provider.

Can you wget the internal ip / port for your rails app directly (or apache) from the same server? This will tell you if probaby is in the application stack or further upstream.

If you can, you can use an apache tool called ab "apache benchmark" to help.

The key has ssh access to your computer.

0


source







All Articles