It has been almost eight years since I first wrote a blog on IIS best practices. During this time, several new versions of IIS have arrived, some reached end of lifecycle; we were introduced a new de...
Updated Apr 17, 2020
Version 2.0
Blog Post
marto871 Yes, there are some recommendations out in the wild that do not align with mine. And STIG has a few of them which do not align. But I will stick with my recommendations on application pool recycling settings; and especially about giving memory limits. If you check "virtual bytes" of any 64bit worker process at any random time, you would see terabytes. This makes giving a limit to virtual memory unnecessary, and even harmful - causing the pool to recycle too often. For both virtual and private memory limits, since they are not actually limits but recycle triggers, that does not make any sense.
There might be some exceptions for private memory limit (like known memory leak issues in the application), but I cannot think of any scenario one would need to set limit to virtual memory.