Andy Wojnarek on 26 Sep 2017 16:00:14 -0700

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]


Hey Ron,


What kind of workload is this? Rule of thumb is that your load average might be appropriate based on the type of workload you’re running. If response time is most important, you may want it no higher than 1 to 2 times the number of CPUs allocated to the host. If Job throughput is important, 3 to 4 times the number of CPUs may be sufficient to keep the processors busy – especially with hyper-threading.


Baseline your load average with some other type of metric at the application level (http response time for example) to determine what is appropriate.


So to answer your question, what number to alert on may be different for the different types of workloads you’re looking to monitor.



Andy Wojnarek


From: plug <> on behalf of Ron Guilmet <>
Reply-To: Philadelphia Linux User's Group Discussion List <>
Date: Tuesday, September 26, 2017 at 3:01 PM
To: plug <>


I had some questions on load averages and Nagios, and the documentations is not very intuitive. My understanding of load averages is that they are in relation to the amount of CPUs a server has. For example, a load of 1.5 on a single core server means processes are beginning to queue up which can lead to slow performance, while a 1.5 load average on a 2 core machine processes are not queuing up.


So with that understanding, I need specific Nagios checks for different systems, correct?

For example, this check may alter me of a problem with one server, but other servers may go down without notice, right?



   Command: "/usr/lib/nagios/plugins/check_load -w  6,5,4 -c 10,8,6"

   Type: NRPE


Thanks Ron



Ron Guilmet

Cloud Solutions Architect


Philadelphia Linux Users Group         --
Announcements -
General Discussion  --