A hard limit stops the application completely
when it has exceeded its memory allocation. This is useful in preventing a runaway
process from completely using up all your server resources. For example, you can
apply this to your IIS worker processes. This way, if a poorly written Web application
suddenly wants to hog all your memory, WSRM will automatically stop it for you, keeping
all your other processes up and running. Unlike the CPU resource limits, the memory
limit you specify applies to each process that falls under that group and isn??™t shared between
them. For example, if you specify 20MB as the maximum limit for a given process
matching criterion, then each process that matches that criterion gets 20MB.
226 Microsoft Windows Server 2008 Administration
Limits can be set on working set or committed memory. Working set memory refers to
the amount of memory used by the process during its runtime. Once the upper limit for
working set memory has been reached, the memory manager begins swapping out the
memory pages. This can reduce the performance of the application somewhat but will
not induce any out-of-memory errors. Committed memory, on the other hand, is used to
watch for errant processes or memory leaks. By setting, a reasonable threshold on your
processes, you can force those processes to stop when they reach the limit or log an entry
in your event log for later troubleshooting.
Pages:
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276