What are the basic steps to troubleshoot slowness of a linux system
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
What are the basic steps to troubleshoot slowness of a linux system
Hi, I am not very much familiar with linux. I know installation, basic services & configuration, but not done the troubleshooting part. Can someone tell me the basic steps to troubleshoot the slowness of a linux system? I tried a few commands like top, vmstat, iostat, sysstat etc. Is there anything else that i shall look into? Please advise.
If it is only a web oriented program that seems slow to start up, one thing to consider is to disable ipv6. Sometimes a dns lookup is tried using it resulting in a delay until it times out.
Please fill in your user info like distribution and such.
In relation to what's said already, "slowness" is not easy to deal with if it's not expressed in values (in other words: perception of speed). In my opinion the best way to start is to set up baseline data like you did with your SAR tools (or Atop or Dstat or Collectl) running for at least 24 hours. This way, if you tweaked things, you'll have objective numbers to compare against. List your hardware, distribution, kernel, any sysctls or other tweaks you already tried (for most of that I still use ServDoc. OK, it's old but it doesn't need to be installed and can output text, HTML, etc.). Data and information together can also help when comparing with other peoples benchmarks, say if you expected higher disk throughput, or directly pinpoint bottlenecks like low RAM, swap usage, wrong scheduler, et cetera. You might also want to search LQ for threads about performance tuning or performance issues, we've got quite some threads. Any questions, just ask.
Basically, you're on the right way. You need to find the process(-es) which consumes a lot of resource such as memory or CPU or disk.
If there are no "crocodiles", try to switch off some unused services and applettes.
Another way is to rebuild the kernel, but it's already the topic of the book, but not the forum post
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.