MssincWe did some research on W3WP not releasing RAM. This AM with just 2 users in VSA, that process was up to 418MB around 10:30AM. We found that there is a garbagecollection process that is supposed to run to free up RAM, but with multiple CPU's it consumes too much. So we have edited aspnet.config and added:
But what seems to have fixed the problem was in IIS Manager/App Pools/Kaseya/Properties we checked the box to limit RAM to 192MB. The W3WP process immediatley went down to 78MB and is now peaking at 148MB.
What are the best practices with this?
Bob Aubry from Pat's login
Main Street Software