How To Check The Cpu Usage In Linux : Linux CPU Usage Monitoring Commands

by

Your server’s CPU usage tells you immediately if a process is consuming too many resources. If you’re wondering how to check the cpu usage in linux, you’ve come to the right place. Monitoring CPU usage is a fundamental skill for any system administrator or developer working with Linux servers. In this guide, we’ll walk you through every major command and tool available, from simple one-liners to real-time monitoring solutions. Whether you’re troubleshooting a slow application or optimizing server performance, knowing how to read CPU metrics will save you hours of frustration.

Linux offers a variety of built-in utilities that give you instant access to CPU data. The best part? Most of these tools are already installed on your system, so you don’t need to download anything extra. We’ll cover commands like top, htop, mpstat, and vmstat, plus graphical alternatives if you prefer a visual interface. By the end of this article, you’ll be able to identify CPU bottlenecks, spot runaway processes, and keep your server running smoothly.

Why Monitoring CPU Usage Matters

CPU usage directly impacts your system’s responsiveness. When a process hogs the CPU, other tasks slow down or freeze. High CPU usage can also indicate malware, memory leaks, or misconfigured applications. Regular monitoring helps you catch these issues early.

Think of your CPU as the brain of your server. If it’s overloaded, everything else suffers. That’s why understanding how to check CPU usage in Linux is a core skill for anyone managing servers. It’s not just about seeing numbers; it’s about interpreting them correctly to make informed decisions.

How To Check The Cpu Usage In Linux

Now let’s get into the actual commands. The exact keyword “How To Check The Cpu Usage In Linux” is your starting point for mastering these tools. Below, we’ll explore each method in detail, from the simplest to the most advanced.

Using The Top Command

The top command is the most widely used tool for real-time CPU monitoring. It displays a dynamic list of processes sorted by CPU usage. Here’s how to use it:

  1. Open your terminal.
  2. Type top and press Enter.
  3. You’ll see a summary at the top showing total CPU usage, load average, and memory stats.
  4. The list below shows each process with its PID, user, CPU%, and more.
  5. Press q to exit.

The default view shows processes sorted by CPU usage in descending order. This makes it easy to spot the most resource-hungry tasks. You can also press Shift + P to sort by CPU percentage again if the order changes.

One limitation of top is that it updates every few seconds, which can be overwhelming on busy systems. But for quick checks, it’s unbeatable.

Using The Htop Command

htop is an improved version of top with a color-coded interface. It’s not installed by default on all distributions, but you can install it easily:

  • On Debian/Ubuntu: sudo apt install htop
  • On RHEL/CentOS: sudo yum install htop
  • On Fedora: sudo dnf install htop

Once installed, run htop in your terminal. You’ll see a visual representation of CPU cores, memory usage, and process trees. You can scroll up and down, kill processes with F9, and change the display settings with F2. It’s much more user-friendly than top.

The key advantage of htop is its interactive nature. You can click buttons or use keyboard shortcuts to manage processes without memorizing complex commands.

Using The Mpstat Command

mpstat is part of the sysstat package and provides detailed per-CPU statistics. It’s excellent for seeing how each core is performing. Install it first:

  • Debian/Ubuntu: sudo apt install sysstat
  • RHEL/CentOS: sudo yum install sysstat

To check overall CPU usage, run:

mpstat

This shows average CPU usage across all cores. To see per-core data, use:

mpstat -P ALL

The output includes columns like %user, %system, %iowait, and %idle. High %iowait indicates disk bottlenecks, while high %system suggests kernel-related issues.

You can also run mpstat at intervals. For example, mpstat 2 5 displays CPU stats every 2 seconds for 5 iterations.

Using The Vmstat Command

vmstat gives a broad view of system performance, including CPU, memory, and I/O. It’s lightweight and perfect for quick health checks. Run it with:

vmstat 1

The first line shows averages since boot. Subsequent lines show real-time data. Focus on the us (user time), sy (system time), id (idle), and wa (wait I/O) columns. If wa is consistently high, your disk might be the problem.

For more detail, add the -t flag to include timestamps: vmstat -t 1.

Using The /Proc/Stat File

All the above commands read data from /proc/stat. You can access it directly for custom monitoring. Use:

cat /proc/stat

The first line shows total CPU time across all cores. The numbers represent time spent in user mode, system mode, idle, etc. To calculate CPU usage, you need to sample the file twice and compute the difference. This is more advanced but gives you full control.

For scripting, you can parse this file with tools like awk or grep. It’s a bit raw, but very powerful.

Using The Sar Command

sar is another tool from the sysstat package. It collects and reports system activity over time. To view CPU usage history, run:

sar -u

This shows CPU usage for the current day. You can specify a different day with sar -u -f /var/log/sysstat/saDD where DD is the day number.

For real-time monitoring, use sar -u 1 3 to get three samples at one-second intervals. The output includes %user, %nice, %system, %iowait, %steal, and %idle.

sar is invaluable for historical analysis. If your server had a spike last night, you can check exactly when it happened.

Using The Ps Command

The ps command shows running processes at a snapshot. To see CPU usage for all processes, use:

ps aux --sort=-%cpu

This lists processes sorted by CPU usage descending. The %CPU column shows the percentage of CPU each process is using. For a more detailed view, try:

ps -eo pid,ppid,cmd,%cpu,%mem --sort=-%cpu

This gives you PID, parent PID, command, CPU%, and memory%. It’s great for scripting or when you need a static list.

Using The Nmon Command

nmon is a performance monitoring tool developed by IBM. It provides a real-time dashboard with CPU, memory, network, and disk stats. Install it with:

  • Debian/Ubuntu: sudo apt install nmon
  • RHEL/CentOS: sudo yum install nmon

Run nmon and press c to view CPU stats. You’ll see per-core utilization as bar graphs. Press q to quit. nmon also supports data capture for later analysis.

Using The Glances Command

glances is a cross-platform monitoring tool with a web interface option. Install it via pip or your package manager:

sudo apt install glances

Run glances to see a colorful dashboard with CPU, memory, network, and disk usage. It updates every second and highlights critical values. You can also run it as a server: glances -w and access it via browser at http://your-ip:61208.

Using The Iostat Command

While iostat focuses on I/O, it also shows CPU usage. Run:

iostat -c

This displays %user, %nice, %system, %iowait, %steal, and %idle. It’s useful when you suspect disk I/O is affecting CPU performance.

Using The Uptime Command

The uptime command shows load averages for 1, 5, and 15 minutes. While not direct CPU usage, load average indicates how many processes are waiting for CPU time. A load average above the number of CPU cores suggests the system is overloaded.

Run uptime to see these values. For example, “load average: 2.50, 1.80, 1.20” on a dual-core system means the CPU is working hard.

Using The W Command

w shows who is logged in and what they’re doing, plus system load averages. It’s a quick way to see if users are running heavy processes. Type w and look at the load average in the first line.

Using The Gnome System Monitor

If you’re using a desktop environment like GNOME, you can use the graphical System Monitor. Open it from the applications menu or run gnome-system-monitor. It shows CPU history graphs, process lists, and resource usage in a friendly interface.

This is ideal for beginners who prefer visuals over command-line tools. You can sort processes, kill them, and see real-time graphs.

Using The Ksysguard Tool

For KDE users, ksysguard offers similar functionality. It’s a system monitor with customizable tabs and sensors. You can add CPU, memory, and network graphs to your dashboard.

Using The Conky Tool

conky is a lightweight system monitor that runs on your desktop. It displays CPU usage, memory, disk, and more in a customizable widget. Install it and configure a .conkyrc file to show exactly what you need.

Using The Dstat Command

dstat combines features of vmstat, iostat, netstat, and more. It’s not installed by default, but you can add it via your package manager. Run:

dstat -c

This shows CPU stats in real-time. You can combine multiple options, like dstat -c -d -n for CPU, disk, and network.

Using The Collectl Command

collectl is a versatile monitoring tool that can log data for later analysis. Run collectl -sc to see CPU stats. It’s great for capturing performance data over time.

Interpreting CPU Usage Metrics

Knowing the commands is only half the battle. You also need to understand what the numbers mean. Here are the key metrics:

  • %user: Time spent running user processes (applications).
  • %system: Time spent running kernel processes.
  • %idle: Time the CPU is idle.
  • %iowait: Time waiting for I/O operations to complete.
  • %steal: Time waiting for a hypervisor to allocate CPU (common in virtualized environments).
  • %nice: Time spent running low-priority user processes.

If %iowait is consistently above 10%, your disk is likely a bottleneck. High %steal suggests your cloud provider is overselling resources. Low %idle means your CPU is busy, which could be normal or problematic depending on context.

Common CPU Usage Scenarios

Let’s look at typical situations you might encounter:

High CPU Usage From A Single Process

If one process uses 100% CPU, it might be a runaway script or a legitimate heavy task. Use top or htop to find the PID, then investigate. You can kill it with kill -9 PID if needed.

High System CPU Usage

If %system is high, the kernel is working hard. This could be due to driver issues, network interrupts, or misconfigured hardware. Check dmesg for errors.

High Iowait

High %iowait means the CPU is waiting for disk or network. Use iostat to identify the slow device. Consider upgrading storage or optimizing queries.

High Steal Time

In cloud environments, high %steal indicates your VM is competing for CPU with neighbors. You may need to upgrade your instance type or move to a less crowded host.

Automating CPU Monitoring

You don’t have to watch CPU usage manually. Set up cron jobs to log data or use tools like monit or nagios for alerts. For example, you can create a script that checks CPU usage every minute and sends an email if it exceeds 90%.

Here’s a simple bash script:

#!/bin/bash
CPU=$(top -bn1 | grep "Cpu(s)" | awk '{print $2}' | cut -d'%' -f1)
if (( $(echo "$CPU > 90" | bc -l) )); then
    echo "High CPU usage: $CPU%" | mail -s "Alert" admin@example.com
fi

Schedule it with crontab -e and add * * * * * /path/to/script.sh.

Frequently Asked Questions

What is the easiest way to check CPU usage in Linux?

The top command is the simplest. Just type top in the terminal and you’ll see CPU usage immediately.

How do I check CPU usage per core?

Use mpstat -P ALL or htop which shows individual core bars.

Can I check historical CPU usage?

Yes, use sar -u from the sysstat package. It logs data daily.

What does %iowait mean?

It’s the percentage of time the CPU is waiting for I/O operations to complete. High values indicate disk or network bottlenecks.

How do I kill a process using too much CPU?

Find the PID with top or ps, then run kill -9 PID. Be careful, as this forcefully terminates the process.

Final Thoughts

Mastering how to check the cpu usage in linux is essential for maintaining server health. With the tools we’ve covered, you can diagnose performance issues, optimize resource allocation, and prevent downtime. Start with top and htop for daily checks, then explore mpstat and sar for deeper analysis. Remember to monitor regularly, not just when problems arise. Your servers will thank you.

Practice these commands on a test system first. The more you use them, the more intuitive they become. And don’t forget to automate alerts so