Troubleshooting High CPU and Memory Usage on Linux

Troubleshooting High CPU and Memory Usage on Linux

Linux server performance can be crippled by mismanaged processes consuming excessive CPU and RAM. Command-line utilities like htop and vmstat provide real-time visibility into these resource-hungry culprits.

Why This Matters

In technical environments, ideal models assume stable resource allocation, but reality often involves memory leaks and greedy applications that force systems into slow swap usage. Failure to monitor these metrics can lead to application crashes and significant latency, impacting end-user experience and operational costs.

Key Insights

• The top command provides a dynamic real-time view of running processes, allowing users to identify top resource consumers by %CPU and %MEM.
• The free -h command offers a snapshot of total, used, and available RAM, where low availability or high swap usage indicates a critical memory shortage.
• Advanced process filtering using ps aux —sort=-%cpu identifies the top 10 CPU-consuming processes for immediate troubleshooting.
• Disk I/O bottlenecks can be pinpointed with iotop, identifying processes that overwhelm system bandwidth through excessive read/write operations.
• Historical trends and CPU contention are tracked via the r column in vmstat, which reports statistics on runnable processes waiting for CPU time.

Working Examples

Displays a dynamic, real-time view of running processes.

top

An interactive, color-coded process viewer for Linux.

htop

Displays human-readable memory usage, including RAM and swap.

free -h

Lists the top 10 processes consuming the most CPU.

ps aux --sort=-%cpu | head -n 10

Lists the top 10 processes consuming the most memory.

ps aux --sort=-%mem | head -n 10

Monitors disk I/O bandwidth usage per process.

sudo iotop

Outputs system statistics every 5 seconds to track memory, paging, and CPU activity.

vmstat 5

Practical Applications

• Use Case: Web servers like Nginx or Apache2 can be tuned by reviewing logs and configuration to prevent CPU hogging. Pitfall: Neglecting to update application dependencies can lead to unpatched bugs causing performance degradation.
• Use Case: Database management for mysqld or redis involves adjusting buffer pool sizes to optimize memory usage. Pitfall: Using restarts as a permanent fix for memory leaks only temporarily clears RAM without addressing the underlying code defect.
• Use Case: Containerized environments use resource limits (CPU and memory) to prevent a single runaway process from affecting the entire host. Pitfall: High kernel-level CPU usage in kworker threads often indicates underlying hardware failures or faulty drivers.

References:

• https://dev.to/big_mazzy_06d057cc24398c5/troubleshooting-high-cpu-and-memory-usage-on-linux-4bon