Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
I found that my Fedora 12 running slowly due to CPU higher usage even I reboot still same issues. I tried to used top to traced which process caused but fail even I sort by CPU, I also can't trace which process caused my CPU higher usage, is there anyone can help me? or other command can help to trace?
I found that my Fedora 12 running slowly due to CPU higher usage even I reboot still same issues. I tried to used top to traced which process caused but fail even I sort by CPU, I also can't trace which process caused my CPU higher usage, is there anyone can help me? or other command can help to trace?
I can't read your text but I think I recognize some kde stuff in there so I'll bite. :-)
Assuming you have KDE.
1. Turn NEPOMUK OFF!! It's a cpu hog and 'locate' does it better and nicer.
2. As superuser, turn /etc/PackageKit OFF!! By renaming the config file. Otherwise it sits there trying to get online every few seconds.
3. If you have ksysguard (Ctrl-ESC or run by typing the name on the commandline) you can click on the top bar and add PID display as well as CPU to the lists and click on the PIDs or CPU times to sort in ascending or descending order.
That will show you who the culprits are and when they started.
View as a 'tree' to see the relationships of the offending apps. You can do that with 'ps' also and probably whatever you got your dump with, if I miss my guess about KDE here.
Also, I just realized that some distros come with Tracker set up by default.
You can uninstall it if that's sucking up cpu time. It has no dependencies on it that I know of and it will hog time like crazy if you have a lot of files in your HOME directory.
Well, what you are asking us to do with that data won't work, and it probably can't work for you, either.
Are you actually saying (you didn't say, but it may be the inference that you intended us to take) that the output that you posted was sorted according to cpu usage? In any case, it only has six tasks, and two of those are tops, one run by root and one by eric (I assume that's you). I'm pretty sure that you have rather more tasks running.
In any case, you will have noticed that most of the cpu percentage is going on (io)wait; this isn't going to show up, broken down by task, in top, so that makes top a rather blunt tool for this kind of problem.
your next step is to find out what is causing the wait; it is probably some kind of IO; so you need to find out if it is disk, network, etc.
Either having done that, (or, potentially slightly more difficult) you need to go around trying to pin down the cause of the IO - it might be immediately apparent, once you know what kind of IO it is (...eg, ok, so the only thing using the network is Blah, and we know it is network IO, so we know it is Blah)
A useful tool, in this kind of circumstance, is iotop. Now, it is easier to go straight to the scene of the criome if you know what kind of IO you are looking for, but if you don't and can't find out, you can just go through the types of IO that it might be, and see which it actually is.
At that point, you've either got some IO that you were expecting, but is chewing up a lot more time than you were expecting (why?) or some IO that you weren't expecting (err, why?, again)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.