![]() ![]() For example, a dual core system with a load average of 0.5 doesn't have any processes waiting and is handling everything with no delays. If the load average is at the same number of cores or close, then the system is doing fine. The rule of thumb is that if the load average is consistently significantly higher than the number of cores in the system, the system can be stressed for resources. Those numbers are the average sum of the number of processes waiting in the run-queue, plus the number currently executing, over 1, 5, and 15-minute time periods.Ī more detailed explanation can be found here: ![]() The System load average warning level of this monitor will send three numbers. Often disk load is the main reason for high load average due to web filter logging and reporting database index creation. This means that a high load does not necessarily mean that the CPU is busy. The load average is an abstract value and uses CPU load, memory load and disk load to create the load average number. It is not just a measure of CPU load but rather an abstract that tries to give a general insight into how well the system is coping with the workload. The load average graph on the Summary page shows an abstract representation of the system workload ( Processor section), see our help topic, About the summary report. The dashboard page is dynamic and will change when the load does. The load average is shown on both the dashboard page and on the Summary Report under the Processor section. An insight into interpretation of the Load average graph and metrics on the Smoothwall. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |