How to Diagnose and Speed Up a Slow Linux Machine: CPU, Services, Memory, and Disk Checks
This guide walks you through practical Linux performance troubleshooting steps, covering how to inspect CPU details, list boot‑time services, monitor CPU load, check free memory, and analyze disk I/O, with concrete commands and solutions to improve system speed.
1. Check CPU Information
Start by examining CPU details, as an under‑powered processor often explains why applications like LibreOffice feel sluggish.
cat /proc/cpuinfo
lscpu
The output shows fields such as vendor_id , model name , CPU MHz, cache size, microcode, and bogomips .
bogomips: a rough indicator of processor speed (Bogo = bogus, MIPS = million instructions per second).
model_name: identifies the CPU vendor, model, and nominal speed (e.g., Intel® Celeron® 1.73 GHz).
CPU MHz: the actual clock frequency (e.g., 1733.329 MHz in the example).
If the CPU is an old, low‑performance model, the only effective remedy is to replace it with a faster processor.
2. Check Services Started at Boot
Identify which services are launched during system start‑up using any of the following commands.
service --status-allFor CentOS, Fedora, and Red Hat compatible systems you can also run:
chkconfig --listAnother option is:
initctl listIf the system uses systemd , list enabled units with: sudo systemctl list-unit-files --state=enabled Solution: use systemctl to enable, disable, or mask services so that unnecessary ones do not start at boot.
3. Check CPU Load
Use top to view real‑time CPU usage and identify processes that consume excessive CPU cycles.
Solution: close or kill unnecessary foreground or background applications, and prevent unwanted programs from running in the background.
Installing preload can also improve perceived performance by keeping frequently used binaries in memory.
sudo apt-get install preload sudo yum install preload4. Check Free Memory Space
Run free to see total, used, and available memory. Low free memory can degrade performance.
Solution: upgrade RAM or replace memory‑hungry applications (e.g., use AbiWord instead of LibreOffice).
5. Check Disk I/O Usage
When the hard‑drive activity light blinks continuously, I/O contention may be the cause. Use iotop to monitor per‑process I/O.
sudo apt install iotop sudo yum install iotopSolution: identify and, if possible, limit I/O‑intensive utilities (e.g., find) that cause high throughput.
Conclusion
Although many factors can slow a Linux system, CPU capacity, available memory, and disk I/O are the primary culprits. Applying the commands and techniques described above helps pinpoint the root cause and provides concrete actions to restore responsive performance.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
ITPUB
Official ITPUB account sharing technical insights, community news, and exciting events.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
