0

I'm experiencing an issue where almost every request for a resource on a web application has a 100ms - 500ms delay in the "connecting" phase as reported by firebug, which is the time it takes to establish a TCP connection.

The server, Nginx, is configured to use keep-alive, and the response headers indicate that keep-alive is on. Yet, every resource that loads on the page has a long "connecting" delay.

This system is not in production and I am the only user making requests against it. Are there any OS variables related to TCP optimization that I should check to find out why each request has a TCP connection delay, even though keep-alive is enabled?

The server is running Ubuntu 14.04 LTS.

  • You are mixing two different things. The slow TCP startup and the HTTP optimization to avoid doing TCP startup. I think the questions deserves a bit of clarification. – Pavel Šimerda Jan 3 '15 at 14:25
  • You would be best off by starting using the "strace" command to see what Nginx is actually doing in that first 100ms-500ms. – Chris Davidson Jan 3 '15 at 14:44

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.