I have several web sites on my windows 2008 server that have been working flawlessly for over a year. Just a few days ago I ran into an issue where my server stopped serving up pages on some of these sites for no apparent reason. I dug into it a little more today and I see that some of my sites (they’re all asp.net mvc 3.0 sites), are consuming over 460MB of memory. Like I said, this just started the other day after a very long period of time of no issues at all.
I have two questions:
1) is there a way to throttle how much memory is consumed by the w3wp process before I can force it to restart (restart the app pool for a particular site) so that it doesn’t keep hogging all of the memory?
2) any ideas what could have caused this to start happening?
Answer
1) is there a way to throttle how much memory is consumed by the w3wp process before I can force
it to restart
No, and it makes no sense because – the apps live in their own processes.
2) any ideas what could have caused this to start happening?
Yes. Bad code. That it as good as it gets without attaching a Debugger. THAT SIAD: 460mbis not exactly a lot of Memory. Can be some bad Caching.
Attribution
Source : Link , Question Author : Charles , Answer Author : TomTom
