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

We're running a somewhat large site and have recently started have performance issues.

If I open FireBug in FireFox and loads up a page, it'll sometimes wait for 6-7 seconds, before receiving the initial page.

Then it'll start requesting javascripts, and they'll wait 6-7 seconds as well.

After maybe 6-8 requests, it'll start serving them with a minimum of wait time (10-20 ms)

We're hosting the site on Windows 2008 R2 running IIS 7.5. The site is in 3.5.

We're also logging the time from PreInit to PreRender, and it's seldomly above 100ms, so it's not the code or database, which causes the initial wait of 6-7 seconds.

And the code/database obviously have no effect on the javascripts (or images), which wait for 6-7 seconds as well.

We're at a loss here, so any help is highly appreciated.

EDIT: We've just discovered that it is in fact the DB, which is causing the trouble. Every 3 minutes a single core peaks in kernel time, and this corresponds with when the site is slow.

Next step is to figure out whether it's a driver or whatnot. (It's the system process)

share|improve this question
Figured it out finally. It seems there's an option to SQL server, which determines whether the OS may page out the SQL server's memory or not. Once we set it to not allow paging, the performance issues went away. – Steffen Jul 5 '10 at 13:15
Steffen, can you exactly describe where that option in sql server? – Denis Elkhov Mar 2 '11 at 8:14

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.