Take direct control of CPU governors and frequencies to tune performance and power on Linux. 06.07.2026 | reading time: 3 min Want to control how the kernel scales CPU speed to save energy or boost performance? `cpupower` is the admin tool that talks to the kernel's cpufreq and idle subsystems so he can inspect governors, set limits per CPU, and apply policies quickly. Limit CPU frequency for a batch job Try this scenario on a test host: he wants to cap CPUs while a long batch job runs to reduce thermals. First inspect current state with: ```bash sudo cpupower frequency-info ``` Sample output: ```text analyzing CPU 0: driver: intel_pstate current policy: frequency should be within 800 MHz and 3.50 GHz. current CPU frequency: 1.20 GHz ``` Set a conservative governor for all CPUs and verify: ```bash sudo cpupower frequency-set -g powersave sudo cpupower frequency-info | grep "current policy" ``` Expected change: the policy line shows the "powersave" governor and observed frequencies trend lower while the job runs. Fine control: per-CPU and exact limits When he needs tighter control, `cpupower` accepts CPU selectors and explicit min/max/fixed frequencies: use `-c` to target CPUs, `-d` to lower the minimum, `-u` to raise the maximum, and `-f` to request a fixed frequency; remember that hardware drivers or the intel_pstate driver may ignore impossible requests and that root privileges are required. Other features worth using Beyond frequency-set and frequency-info, `cpupower` offers monitoring subcommands and x86-specific info, and it can be run at boot via a systemd unit to persist policies; combine it with governor-aware tuning and test workloads to validate system behavior rather than guessing. Tools that play well with cpupower In production he often pairs `cpupower` with power and thermal utilities to get a complete picture: `powertop` to spot wakeups, `tuned` for profile-based tuning, and `thermald` for temperature control; pick the tool that fits the use case and avoid fighting multiple services that set governors. Quick precautions Changing governors and frequencies can impact latency, throughput, and battery life; test settings under representative load, be aware that some drivers (for example intel_pstate) enforce their own policies, and prefer scripted changes and systemd services for repeatability. Wrap-up and next steps Now he can inspect, set, and script CPU policies with `cpupower` to balance energy and performance; practice on nonproduction machines, combine results with monitoring tools, and consider formal study to deepen knowledge and prepare for certifications like CompTIA Linux+ or LPIC-1 with intensive exam preparation at bitsandbytes.academy. Join Bits & Bytes Academy First class LINUX exam preparation. processes utilities boot-process troubleshooting This page was created with the help of AI.
