WSRM isn??™t actually involved in the memory
allocation. This is the job of the memory manager. WSRM??™s job is to monitor utilization,
and if it exceeds that utilization, inform the memory manager so it can adjust or even
deny additional memory from being allocated to that process.
You can also specify additional advanced options. On a multiprocessor system, you
can specify exactly which processor or processors each process is allowed to use. You can
also optionally suballocate processor resources. For example, if you had four processors
on your server and you allocate two processors for a specific process matching criterion,
you can then use suballocation to specify how those two processors should be split up
between the processes. This creates a parent/child relationship between an allocation
and its suballocation. You??™re not limited to one level of parent/child relationship. A
child can have its own children, so you can have multi-level allocation relationships. The
allocation begins at the lowest level, and any available resources are then made available
to the parent, until finally any remaining resources are made available to the default
group. This is referred to as a priority-order chain.
Hands-On Exercise: Creating a CPU Allocation Policy
In this simple example, we will use the AllNotepad process matching criterion to limit
any notepad.exe processes to use only 10 percent CPU and up to 10MB of memory at
any given time.
Pages:
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277