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.
You need to find out what's using the memory and see if you need all the programs (maybe there are services started at boot and you don't need them?). To see the amount of memory used by all applications use
ps aux
command. Memory usage (in %) is in the 4th column. Check for most memory-hungry programs. If you're unsure if you can turn them off, post their names.
Also try running top, which sorts the processes in order of most CPU usage to least. Sometimes it's easy to miss a CPU-hog in a long list, but with top, the biggest process will appear first, making it hard to miss.
Personally I do not think it would be necessary to switch distros. I would be willing to bet that you just have a runaway process eating those CPU cycles. -- J.W.
No, just offering a possibility. The above commands won't hurt your disk; check the man pages for "hdparm" and "smartd". Run them, then think about whether or not the disk could be a problem. Maybe the way your database is set up is causing seek time problems ? I don't know, just some things to consider, since you seem to have plenty of cpu and memory to spare.
It's usual for httpd and mysqld to have multiple instances, though, helps out when faced with multiple requests I believe.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.