The amount of CPU time that each scheduler partition tends to use under unloaded conditions is a good indication of the budget you should assign to it. If your application is a transaction processor, it may be useful to measure CPU consumption under a few different loads and construct a graph of offered load versus the CPU consumed.
Typically, the key to obtaining the right combination of partition budgets is to try them:
-
Leave security turned off.
-
Load a test machine with realistic loads.
-
Examine the latencies of your time-sensitive threads with the IDE's System Profiler tool.
-
Try different patterns of budgets, which you can easily change at run time with the
aps
command.
Note: You can't delete a partition, but you can remove all of its corresponding processes, and then change that specific partition's budget to 0%.