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.
Load average is misleading, it is really the queue delay on processing which can reflect real CPU load, memory, or process queue issues. If it has not climbed above 5 during hot processing (under stress) then no worries. IF it hits 8 or 9 you have to have a close look at what is going on, you DO have a problem. If it is in the 0-3 range that is pretty normal.
What things can push it up will depend upon your specific hardware, configuration, and usage.
I always thought, if your load average is less than your CPU cores, then everything funning at full speed. If its higher than your number of cores, then your cpu is the bottleneck.
from my side, the three numbers next to that load average do not mean a lot. Also you cannot compare hosts to check if it is good enough or not. I would rather go from the other direction. Based on your own experience you can collect some data (let's say yesterday 10 was ok, so it will be ok today too).
I would recommend you to ignore it and use idle time instead (3rd line: %Cpu, .... 25.9 id). If it is too low (< 10) your host is busy, and may slow down.
It makes sense to monitor the system load.
The sum of the compute-CPUs is a good alert threshold for load.
If the load is caused by computation then this threshold is precise - all CPUs are saturated.
If the load is caused by something else then there is congestion elsewhere.
I remember a dozen applications were frequently locking files on NFS; the NFS server couldn't keep up; the application processes went to D state, and the load was about the sum of the D states. Thanks to the load alert this was brought to light, could be analyzed, and finanally the application was fixed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.