Learn how to lower a process priority so heavy jobs behave and the system stays responsive. 16.04.2026 | reading time: 2 min A single greedy job can make a desktop slow or a server unresponsive; the `nice` command lets a user lower a process priority so other work stays snappy. Hands-on demo Start a low-priority background job and inspect its niceness with this quick test. ``` # start a CPU-bound job with low priority and check its niceness nice -n 19 python3 -c 'for i in range(10000000): pass' & pid=$! ps -o pid,ni,cmd -p $pid # example output # PID NI CMD # 12345 19 python3 -c 'for i in range(10000000): pass' ``` Important details to remember `nice` without options increases niceness by 10; the full niceness range is -20 (highest priority) to 19 (lowest) and only root can set negative values; use `renice` to change the niceness of a running process and `ps`, `top` or `htop` to view the NI column. Practical use cases Use `nice` for batch jobs, large compiles, backups or video encoding so interactive sessions remain responsive; do not rely on `nice` for real-time guarantees, and be aware it affects CPU scheduling priority but not IO fairness. Combine and caution Combine `nice` with `ionice` for IO-heavy tasks or with cgroups for stronger limits; remember `nice` is about politeness, not absolute throttling, so a very low-priority process can still starve short-lived real-time tasks if misused. Where to go next Try `renice` on a running PID, experiment with different niceness values, and then explore IO and cgroup controls; deepen your Linux skills and consider exam-focused training such as CompTIA Linux+ or LPIC-1 at bitsandbytes.academy for certification preparation. Join Bits & Bytes Academy First class LINUX exam preparation. processes utilities troubleshooting scripting infrastructure
