How to Check CPU and Memory Usage on Linux
Diagnose performance issues by analyzing CPU load, memory usage, and running processes.
Before you start
Step-by-step instructions
1. Use top for real-time system overview
Start with top to see real-time CPU and memory usage. This is the fastest way to identify whether the system is under load.
topWatch CPU usage, load average, and the process list. Sort by CPU or memory to find the heaviest processes.
2. Use htop for better visualization (if available)
htop provides a clearer and more interactive interface compared to top. It allows easier sorting and process management.
htopIf htop is not installed, you can install it or continue using top. Both provide the necessary information.
3. Check memory usage with free
Use free to quickly check total, used, and available memory. This helps you understand whether the system is under memory pressure.
free -hFocus on available memory rather than used memory. Linux uses memory for caching, which is normal behavior.
4. Identify high-resource processes
Once you detect high usage, identify which processes are responsible. This is where troubleshooting becomes actionable.
ps aux --sort=-%cpu | headThis quickly shows the top CPU-consuming processes so you can investigate or optimize them.
5. Interpret the results before taking action
Do not immediately kill processes or restart services. First understand whether the load is expected, temporary, or caused by a specific issue.
A spike during backup or batch processing is normal. Continuous high usage with performance impact is what requires investigation.
Real example
A server becomes slow during peak hours. Using top, an administrator sees one process consistently using high CPU. Further inspection shows it is a poorly optimized query in a backend service. Fixing the query resolves the performance issue without needing to scale the server.
This demonstrates why identifying the correct process is more important than reacting to overall usage numbers.
Possible causes
- High traffic or workload spikes
- Inefficient application logic or queries
- Background jobs or batch processes
- Memory leaks in long-running services
- Insufficient system resources
Common mistakes
- Assuming high memory usage is always a problem
- Killing processes without understanding their role
- Ignoring load average and focusing only on CPU percentage
- Not checking historical or recurring patterns
- Restarting services instead of fixing root causes
Environment tips
- Use
topfor quick checks andhtopfor interactive analysis. - Always check
free -hto understand memory availability. - Use
ps aux --sort=-%cputo identify heavy processes quickly. - Combine CPU, memory, and load information before making decisions.
About this guide
This guide shows how to check CPU and memory usage on Linux using real-world commands such as top, htop, and free. It focuses on practical troubleshooting so you can quickly identify performance bottlenecks, high-load processes, and memory pressure conditions.
How to follow this guide
- Use top to get a real-time overview of CPU and memory usage.
- Use htop for a clearer and more interactive process view if available.
- Use free -h to quickly check total, used, and available memory.
- Identify which processes consume the most CPU or RAM.
- Interpret load average and memory usage correctly before taking action.
Why use this method?
High CPU or memory usage is one of the most common causes of slow servers, timeouts, and crashes. Knowing how to quickly read system metrics helps you determine whether the issue is resource exhaustion, a specific process, or an abnormal workload pattern.
Frequently Asked Questions
What is the difference between CPU usage and load average?
CPU usage shows how busy the CPU is right now, while load average represents the number of processes waiting for CPU time. A high load average can indicate CPU saturation or blocked processes.
Why is memory usage always high on Linux?
Linux uses available memory for caching to improve performance. High usage is not always a problem. The important value is available memory, not just used memory.
Is htop better than top?
htop provides a more user-friendly and interactive interface, but top is available by default on most systems and is sufficient for most troubleshooting tasks.
When should I worry about memory usage?
You should investigate when available memory is low, swap usage is increasing, or processes are being killed due to memory pressure.