Summary
This summary discusses the elements of the cpuplugd configuration file in detail and the recommended settings.
See cpuplugd configuration files for details about the tested configuration files. A sample configuration file named cpuplugd is available in /etc/sysconfig for each installation.
When testing the impact of various rules, it is recommended to avoid rules which cause a system to oscillate with a high frequency. This means that in a very short time period resources are repeatedly added and withdrawn. When the workload itself is oscillating with a high frequency, it might help to use average values over larger time periods and decrease the limits.
The opposite behavior is a very sensitive system which reacts very quickly to load changes to cover peak workloads. But even in this scenario, when these load peaks occur very quickly, it might be better to hold the resources.
- Managing the memory of a Linux™ guest with the cpuplugd daemon, rules out the usage of VM Resource Manager (VMRM) Cooperative Memory Management for this guest.
- Managing the CPUs of a Linux guest with the cpuplugd daemon is incompatible with task bindings using the task_set command or the cgroups mechanism.