nice and renice — Managing Process Priorities in Linux¶

Linux allows multiple processes to compete for CPU time. The nice and renice commands help control process scheduling priority, allowing administrators to favor important workloads while reducing the impact of less critical tasks. Proper use of process priorities improves system responsiveness and overall performance in production environments.

Learning Path¶

Linux Mastery → Module 6: Process Management → Lesson 6

Difficulty: Beginner → Intermediate

Reading Time: 55 Minutes

Course Progress

Course: Linux Mastery

Module: Process Management

Lesson: 6 of 10

What You'll Learn¶

After completing this lesson, you'll be able to:

Understand process priority
Learn nice values
Start processes with custom priorities
Change the priority of running processes
Understand CPU scheduling
Improve application performance
Apply priority management in production

Prerequisites¶

Complete:

Module 1 – Linux Fundamentals
Module 2 – Linux Command Line Essentials
Module 3 – Text Processing
Module 4 – File Management and Permissions
Module 5 – Users and Groups
Module 6 Lessons 1–5

Why Learn nice?¶

Imagine a production server running:

Database
Web Server
Backup Job
Log Compression
File Synchronization

The backup job suddenly consumes all available CPU.

Users begin experiencing slow application performance.

Should the backup receive the same CPU priority as the database?

No.

Linux allows us to assign different priorities.

What is Process Priority?¶

Linux schedules CPU time based on process priority.

Higher-priority processes generally receive CPU time before lower-priority processes when CPU resources are limited.

Priority can be adjusted using:

nice
renice

What is a Nice Value?¶

A nice value tells the Linux scheduler how "nice" a process should be to other processes.

A higher nice value means the process is more willing to yield CPU time.

A lower nice value means the process receives higher scheduling priority.

Nice Value Range¶

-20  -------------------->  19

Highest Priority          Lowest Priority

Nice Value	Meaning
-20	Highest priority
0	Default priority
19	Lowest priority

Note

Regular users can usually increase the nice value (lower priority) for their own processes. Lowering the nice value (raising priority) generally requires administrative privileges.

View Nice Values¶

Display running processes.

ps -el

Example:

PID PRI NI CMD

245 20 0 bash

600 20 5 backup.sh

Observe:

NI

This represents the nice value.

Start a Process with a Nice Value¶

Default:

python app.py

Lower priority:

nice -n 10 python app.py

Verify:

ps -el

Highest User Priority¶

Administrator only.

sudo nice -n -10 python app.py

This gives the process a higher scheduling priority.

Change Priority of a Running Process¶

Use:

renice

Example:

sudo renice 5 -p 1234

Meaning:

PID

1234

↓

Nice Value

5

Increase Priority¶

Example:

sudo renice -10 -p 1234

Requires administrative privileges.

Decrease Priority¶

Example:

renice 15 -p 1234

Regular users can generally lower the priority of their own processes by increasing the nice value.

View Process Priority¶

ps -o pid,ni,comm

Example:

PID NI COMMAND

1200 0 nginx

2400 10 backup

CPU Scheduling Example¶

Database

NI = -5

↓

Web Server

NI = 0

↓

Backup Job

NI = 15

The scheduler generally favors higher-priority processes when CPU resources are constrained.

Common Commands¶

Start with default priority.

command

Start with custom priority.

nice -n 10 command

Change priority.

renice 10 -p PID

View priority.

ps -el

Display nice values.

ps -o pid,ni,comm

Real Production Examples¶

Low-priority backup.

nice -n 15 tar -czf backup.tar.gz /data

Database maintenance.

nice -n 5 vacuumdb

Log compression.

nice -n 19 gzip large.log

Long-running reports.

nice -n 10 python report.py

Production Perspective¶

Process priorities are useful for:

Database maintenance
Backup jobs
Log processing
File synchronization
Batch processing
CI/CD runners
Data analytics
Large file compression

They help ensure background workloads don't unnecessarily impact interactive users or critical services.

Hands-on Lab¶

Task 1¶

Start a low-priority process.

nice -n 10 sleep 300

Task 2¶

Find its PID.

ps -ef | grep sleep

Task 3¶

Display nice values.

ps -o pid,ni,comm

Task 4¶

Change the priority.

renice 15 -p PID

Replace PID with the process ID from the previous task.

Task 5¶

Verify the change.

ps -o pid,ni,comm

Task 6¶

Display detailed process information.

ps -el

Task 7¶

Start another process with the default priority.

sleep 300

Compare the nice values.

Task 8¶

Terminate the test processes.

kill PID

Command Deep Dive¶

Command	Purpose	Production Example
`nice`	Start a process with a custom priority	Batch jobs
`renice`	Change a running process priority	Performance tuning
`ps -el`	Display priorities	Monitoring
`ps -o pid,ni,comm`	Display nice values	Troubleshooting

Production Troubleshooting Scenario¶

Scenario

A nightly backup begins at midnight.

Users report:

Slow application response
High CPU utilization

Investigation:

top

ps -el

Findings:

The backup process is running with the default priority.

Solution:

Lower its scheduling priority.

sudo renice 15 -p 3456

Result:

Backup continues running.
Business applications receive CPU time more quickly.
Overall system responsiveness improves.

Best Practices¶

Run non-critical batch jobs with higher nice values (lower priority).
Keep critical services at the default priority unless tuning is necessary.
Increase process priority only when justified.
Monitor CPU utilization before changing priorities.
Test priority changes in non-production environments.

Common Mistakes¶

❌ Assigning the highest priority to every application.

✅ This defeats the purpose of process prioritization.

❌ Using negative nice values without understanding their impact.

✅ High-priority processes can reduce CPU availability for other workloads.

❌ Assuming nice changes process memory usage.

✅ It only influences CPU scheduling priority.

Interview Questions¶

Beginner¶

What is a nice value?
What is the default nice value?
Which command starts a process with a custom priority?
Which command changes the priority of a running process?

Intermediate¶

What is the valid range of nice values?
Why do lower nice values result in higher priority?
When would you use renice instead of nice?
How do you display a process's nice value?

Architect Level¶

How would you prioritize workloads on a busy production server?
Which workloads should typically run with lower priority?
Why is process priority tuning important for enterprise Linux systems?

Summary¶

In this lesson, you learned:

Process priorities
Nice values
The nice command
The renice command
CPU scheduling
Priority management
Production best practices

Linux process priorities help administrators balance competing workloads by controlling CPU scheduling. Proper use of nice and renice improves system responsiveness and ensures critical applications receive appropriate CPU resources.

Key Takeaways¶

Nice values range from -20 (highest priority) to 19 (lowest priority).
The default nice value is 0.
Use nice to start a process with a custom priority.
Use renice to modify the priority of a running process.
Lower-priority background jobs should typically have higher nice values.
Use process priorities carefully to maintain system performance.

What's Next?¶

The kill Command — Terminating Processes in Linux

You'll explore:

Terminating processes
Finding Process IDs (PIDs)
Graceful vs forceful termination
Killing multiple processes
Common termination signals
Production troubleshooting

Understanding process termination is an essential skill for managing Linux systems safely and effectively.