Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I am migrating a old server to a new box and i am attempting to clean it up. This box has 600+ sites running on it. I wanted to know what the best practices would be for site pooling. These sites are for small businesses and some get more traffic then others. I was thinking that high traffic sites should get there own pool. Is that correct?

How many low traffic sites can you put in 1 pool?

share|improve this question

closed as primarily opinion-based by Rex, mdpc, Ward, kce, squillman Jun 6 at 19:46

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.If this question can be reworded to fit the rules in the help center, please edit the question.

1 Answer 1

up vote 1 down vote accepted

There isn't a best practice per se, but there are some considerations; some of which you've already thought of, such as traffic. The other considerations are CPU and RAM usage from the resulting traffic to these sites. Generally I like to separate sites on their own Application Pools if at all possible. But in your case you've got 600+ sites, you'll likely end up sharing some pools. The downside of this is that if you have to do maintenance on one site and it requires any sort of recycling or stopping and/or editing of the pools then you'll affect all sites sharing that pool. What I'd do is find a way to break them all down to a group of pools based on traffic and then go from there. Low, Medium, and Large traffic if you can. I'd first recommend reading this.

There's no rule or policy stating that you have to have 1 site per pool for best performance, however, the more separation the better.

share|improve this answer

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