Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

With a 4Gb RAM server and Windows 2003, I've determined by trial and error that setting a virtual RAM limit of 1.6 seems to kill the runaway processes without causing the normal processes to restart unnecessarily.

Support suggested a formula of 1.9 - all running processes = virtual memory limit, is there any theory behind this?

share|improve this question
I remember 800 MB as the "magical" treshold, but I may be wrong... – splattne Jul 27 '09 at 12:05

in theory the value should depend on the website/application running on the app pool

share|improve this answer

I think that the reason to use lower limits is the overlapping recycling that iis does. During the recycling there is a period of time that the old process will run side by side with the new process. You have to consider how this will affect the total memory usage of the server.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.