For example, if you specify 25 percent CPU processing for a particular
process matching criterion, all processes that fall within that criterion must
equally share the 25 percent CPU. In other words, if you had five processes
matching that criterion, each process would get only 5 percent of the CPU
cycles.
?–? Equal per user Similar to Equal per process except it groups processes by
user who initiated them. This is useful in a terminal server environment.
For multiprocessor systems, it gets even more complicated. The percentage reflects
the percentage compared to your overall CPU bandwidth constraints. For example, if
you have four processors and you specify 25 percent to divide between your managed
processes, the 25 percent of your total CPU bandwidth that you then specified means
that instead of having 100 percent of one CPU for your process, you have only 50 percent
of one CPU (25 percent of two CPUs = 50 percent of one CPU). What this all really means
at the end of the day is that you have to minimize the amount of unmanaged processes to
make WSRM??™s resource management effective. Outside of the system-defined exclusion
list, you should avoid excluding processes as much as possible. The amount of memory
you allocate to each of your matching criterion is limited only by the amount of memory
you have on your system. You can create soft or hard limits. A soft limit is implemented
in the form of an event log entry that??™s generated when a process matching your criteria
exceeds the maximum memory allocated to it.
Pages:
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275