Author: bepnewt | Posted on: 5/28/2009 7:03:24 AM | Views : 1042

We have a Framework 3.5 application that deteriorates quickly when the w3wp.exe App Pool process gets to a certain memory usage. The users browser will start clocking and the page they are attempting to load either doesn't load or gets partially loaded and never finishes.
The application is in its own App Pool. The App Pool is set up to recycle at 2:00am and when the used memory gets to 650mb. The Request queue limit is set to 4000. Everything else is set to the defaul.
This is a low-use application. We typically have about 5-15 people logged in at once with maybe 2-4 of them actively working and requesting pages at one time.
The database server is MSSQL 2000. We're using connection pooling and are not setting a maximum number of connections.
The web server is a newly installed 2003 server.
Short history: The web application was on our old production server ( also 2003 ) and was exhibiting the same behavior. It wou ...

Go to the complete details ...