Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We recently migrated our 32 bit web application to 2008 Server R2 64 bit on IIS 7.5, with 8GB or RAM
Generally fine: some minor issues, but this afternoon we got a few out of memory exceptions.
I recyled the app pool, which resolved the issue. We didn’t see this on IIS 6 / W2k3, so I’m digging around to see if we’ve lost some configuration.
Given the app is 32 bit, what should I set as the virtual and private memory limits to trigger app pool recycling?
I asked a related question here : 64 bit OS / 32 bit process
It seems the upper limit for the worker process is 2800 mb