M
Mark
Hi...
We've been trying to migrate our asp.net apps off older, underpowered
hardware to newer, bigger boxes but when we do, we see our databases start to
melt.
When I started to look into it, I found that the older boxes all had bigger
EffectivePrivateBytesLimit values than the newer boxes, which seems very
counter-intuitive to me. And it seemed to me that a much smaller Cache would
be pushing more requests back to the databases.
The old boxes have 2gb physical ram and 3gb pagefile space set aside. The
newer boxes start at 3gb physical ram and 4gb pagefile space and go up from
there.
We're not setting any of the machine.config values or IIS Admin settings
that would curb the cache size on any of the boxes. And we have only one
worker process on all of them. All boxes are running Windows 2003 SP2 and
ASP.Net 2.0.
On the smaller boxes, EffectivePrivateBytesLimit = ~60% of physical ram
(1.2gb). On the bigger boxes, EffectivePrivateBytesLimit = 800mb.
I found this thread: http://forums.asp.net/p/962451/1199949.aspx
Neither of the msdn articles mentioned in it are at those locations anymore,
but the rules of thumb in the response indicate that the bigger boxes *think*
they have <= 2gb of page file.
Is there some kind of overflow/signed condition in Windows 2003 or ASP.Net
2.0 where adding too much gig and/or page file ends up having a negative
effect because the system can't tell?
Thanks
Mark
We've been trying to migrate our asp.net apps off older, underpowered
hardware to newer, bigger boxes but when we do, we see our databases start to
melt.
When I started to look into it, I found that the older boxes all had bigger
EffectivePrivateBytesLimit values than the newer boxes, which seems very
counter-intuitive to me. And it seemed to me that a much smaller Cache would
be pushing more requests back to the databases.
The old boxes have 2gb physical ram and 3gb pagefile space set aside. The
newer boxes start at 3gb physical ram and 4gb pagefile space and go up from
there.
We're not setting any of the machine.config values or IIS Admin settings
that would curb the cache size on any of the boxes. And we have only one
worker process on all of them. All boxes are running Windows 2003 SP2 and
ASP.Net 2.0.
On the smaller boxes, EffectivePrivateBytesLimit = ~60% of physical ram
(1.2gb). On the bigger boxes, EffectivePrivateBytesLimit = 800mb.
I found this thread: http://forums.asp.net/p/962451/1199949.aspx
Neither of the msdn articles mentioned in it are at those locations anymore,
but the rules of thumb in the response indicate that the bigger boxes *think*
they have <= 2gb of page file.
Is there some kind of overflow/signed condition in Windows 2003 or ASP.Net
2.0 where adding too much gig and/or page file ends up having a negative
effect because the system can't tell?
Thanks
Mark