Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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

I've got a 64-bit Server 2008 (R1) box running IIS. Users were complaining about extremely slow-loading pages. After digging around I found:

  1. After isolating the box so only one user was able to connect, each web request caused the CPU to jump to 30% for about two seconds, even on the simplest of pages. Looking at the code, no obvious reason for this usage is apparent.

  2. NewRelic shows > 10s lost to "networking", even though all the access is over a 100-meg LAN, and perfmon shows a network Output Queue Length of zero.

We can't find anything in the code that should cause so much CPU activity, or any answer to why NewRelic thinks there's a network problem.

Looking for suggestions of where to go from here.

share|improve this question

You might also find Failed Request Tracing useful here. The name is a little too specific actually, cause the feature enables tracing any type of request.

Tess Ferrandez over at MSDN wrote a brilliant article about performance troubleshooting with Failed Request Tracing, definitely worth a read in this type of scenario

share|improve this answer

Windows Server 2008 enabled a new network feature by default Scalable Networking Pak. I think this feature causes more issues than it solves. Here is 2 articles refer to this issue:
TCP Chimney
Microsoft Support article: KB951037

share|improve this answer

Your Answer


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

Not the answer you're looking for? Browse other questions tagged or ask your own question.