AppPool memory consumption for shared hosting

I am concerned about the potential memory consumption of multiple
AppPools in a shared hosting scenario. Given ~350 concurrent w3wp
processes (one AppPool for each site), memory will quickly be eaten up.
I am noticing about 35MB memory usage by w3wp.exe for the most trivial
of .aspx pages being served. Doing a little quick math, this gives
~12GB physical RAM usage for 350 concurrent AppPools ?!

What's the best way to tune/balance AppPool usage for shared hosting? I
really want to maintain isolation for each website, by putting each in
its own AppPool, but not at the cost of going beyond 8GB RAM per web
server.

John
Tue Feb 08 09:55:50 CST 2005

On 6 Feb 2005 08:33:29 -0800, "Mark A. Richman"
<markarichman@gmail.com> wrote:

>I am concerned about the potential memory consumption of multiple
>AppPools in a shared hosting scenario. Given ~350 concurrent w3wp
>processes (one AppPool for each site), memory will quickly be eaten up.
>I am noticing about 35MB memory usage by w3wp.exe for the most trivial
>of .aspx pages being served. Doing a little quick math, this gives
>~12GB physical RAM usage for 350 concurrent AppPools ?!
>
>What's the best way to tune/balance AppPool usage for shared hosting? I
>really want to maintain isolation for each website, by putting each in
>its own AppPool, but not at the cost of going beyond 8GB RAM per web
>server.

A shared hosting environment is prime for individual appPools but as
you can see it's not very practical.

John Cesta

The CPU Checker - Monitors your CPU % while you sleep
LogFileManager - IIS LogFile Management Tool
WebPageChecker - Helps Maintain Server UpTime
DomainReportIt PRO - Helps Rebuild IIS
http://www.serverautomationtools.com

Kristofer
Tue Feb 08 12:00:28 CST 2005

Hi Mark,

It is a very good idea to give each customer a dedicated application pool.
Both for security, and availability of the customer's website.

But as you have noticed, this consumes more resources. A practical
limitation is about 250 application pools per server.

There are ways however to cut down the number of application pools. For
example if you offer a static-only solution to your customers, you can
configure all these customers in the same application pool. There is a
very small risk in doing this (since nothing is executed by these websites
on the server).

You can also configure a shorter time when the application should shut
down after being idle.

Just remember to not try to run too many customers on the same server.
They might not be happy with performance, and change to another service
provider...

I dont think that there is any simple solution to this problem. You will
probably have to monitor performance and see when free resources are
getting low, and consider to add a new server.

--
Regards,
Kristofer Gafvert
www.gafvert.info - My Articles and help
www.ilopia.com


Mark A. Richman wrote:

> I am concerned about the potential memory consumption of multiple
> AppPools in a shared hosting scenario. Given ~350 concurrent w3wp
> processes (one AppPool for each site), memory will quickly be eaten up.
> I am noticing about 35MB memory usage by w3wp.exe for the most trivial
> of .aspx pages being served. Doing a little quick math, this gives
> ~12GB physical RAM usage for 350 concurrent AppPools ?!
>
> What's the best way to tune/balance AppPool usage for shared hosting? I
> really want to maintain isolation for each website, by putting each in
> its own AppPool, but not at the cost of going beyond 8GB RAM per web
> server.