It is not that much of a problem when you have one or two app pools, but in
production we have 8 app pools. So the first user to each pool automtahcially
allocates 100MB to the pool. With 8 pools active that mounts up. What I am
wondering is how the WPW3 process will behave when it does its next
allocation. Is it going to go up by 100MB or 64MB. OPUr pools peak at 300MB
during high demand.
We have been looking at this for over a week and cant seem to find any
explaination excpet our own theory that having had .Net on the production
machine the W3WP process is loading extra DLL's a filters even though we have
removed .Net, removed any filters associated with .nmet from the virtual dir
and droped any http headers etc that were setup.
JUst to elobrate a bit more the W3WP process goes to 114MB when the FIRST
user touches the DEFAULT.ASP page. We are loading a COM in this page but yet
again we load the same COM on the other box and onlky use 14MB when the first
user touches the page.
Any Help appreciated as we are a bit stumbled.
"Bob Barrows [MVP]" wrote:
Sean wrote:
I have two win2003 sp1 servers running iis 6.0 running the same
application. When I connected to the first server a W3WP process
(application pool is created) whoose size is approax 14MB When I
connect to the other machine the size is approx 114MB. Does anyone
have any idea what the extra 100 MB is being used for
One Thing to note .NEt 1.1 was installed on the server consuming the
100MB. I have removed the extension and uninstalkled the Asp Net
componment from machine.
I have looked at the metabase of both servers and they seem to be the
same.
Can anyone help.?
I believe it maybe a throw back to the .Net installation but am at a
loss.
I don't know why it is larger (could you have debugging enabled on one
but not the other?), but am wondering why the extra size is a problem
for you.
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.