Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Without touching the server at all, my IIS 7 suddenly got terribly slow. No matter if I request a static content, a php script via FastCGI or a ASP.NET page, it sometimes takes more than 30 seconds for the server to send the response (even for a 1k static file). The resources are not utilized at all (~1% CPU, enough main memory free). The failed request trace from IIS shows for all those slow responses for every step 0ms processing time, but a total processing time of a few thousand milliseconds. It's also not a networking issue (Apache on the same server runs smooth and the same latency applies for local requests). Anyone has an idea what else to test/check? Have you seen such behavior as well?

share|improve this question

migrated from Oct 10 '12 at 5:38

This question came from our site for professional and enthusiast programmers.

You're saying using Apache locally provides the same latency? What is your benchmark for remote calls to both web server instances? – Joel Etherton Oct 9 '12 at 13:36
Is your hard drive dying? – Wug Oct 9 '12 at 13:36
Using Apache remotely provides the same latency (Apache running on the exact same server). The hard drive is just fine, as Apache has no problems reading from it. – skulli Oct 9 '12 at 16:25
Sorry, I meant much better latency and not the same.. So whatever webserver I test with, the results are way better than with IIS. Therefore it's definitely not a networking issue. – skulli Oct 10 '12 at 6:44

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.