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

On Windows 2003 (32 bit Standard Edition with 4GB of RAM) we would host around 1200 sites on a single server split across say 4 application pools. This has worked well for us for a number of years.

IIS7 seems to favour creating a separate application pool for each site and I am lead to believe that IIS application pools are somehow tuned better for this purpose.

Has anyone in the community had experience of this approach with large numbers of sites on a single server?

share|improve this question

If you managed to run it on Windows 2003 it should run on 2008

This case study claims that they can have 3000 application pools per server:

share|improve this answer
In the question it says we run with ~1200 sites spread across a small number of app pools. I'm wondering about how well this would scale where each site has it's own app pool. But thanks for the linky though. – Kev Sep 11 '09 at 1:37
They are running 3000 sites each with their own app pool, so it should work for you, with similar hardware. – Shiraz Bhaiji Sep 11 '09 at 7:03

The most I've gotten up to is about 20 sites per server, so nothing near your numbers. I've got one app pool per site, and haven't had any problems.

I'm running on Web Edition with 2 Gigs of RAM per server.

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.