2016-03-02 15:29:19 +03:00
|
|
|
.. _load:
|
|
|
|
|
|
|
|
|
|
Load
|
|
|
|
|
====
|
|
|
|
|
|
|
|
|
|
*Availability: Unix*
|
|
|
|
|
|
|
|
|
|
.. image:: ../_static/load.png
|
|
|
|
|
|
2017-06-27 22:13:26 +03:00
|
|
|
On the *No Sheep* blog, Zachary Tirrell defines the `load average`_
|
|
|
|
|
on GNU/Linux operating system:
|
2016-03-02 15:29:19 +03:00
|
|
|
|
|
|
|
|
"In short it is the average sum of the number of processes
|
|
|
|
|
waiting in the run-queue plus the number currently executing
|
|
|
|
|
over 1, 5, and 15 minutes time periods."
|
|
|
|
|
|
2017-06-27 22:13:26 +03:00
|
|
|
Be aware that Load on Linux and BSD are different things, high
|
2017-10-23 16:10:41 +03:00
|
|
|
`load on BSD`_ does not means high CPU load.
|
2017-06-27 22:13:26 +03:00
|
|
|
|
2016-03-02 15:29:19 +03:00
|
|
|
Glances gets the number of CPU core to adapt the alerts.
|
|
|
|
|
Alerts on load average are only set on 15 minutes time period.
|
|
|
|
|
The first line also displays the number of CPU core.
|
|
|
|
|
|
|
|
|
|
Legend:
|
|
|
|
|
|
|
|
|
|
============= ============
|
|
|
|
|
Load avg Status
|
|
|
|
|
============= ============
|
|
|
|
|
``<0.7*core`` ``OK``
|
|
|
|
|
``>0.7*core`` ``CAREFUL``
|
|
|
|
|
``>1*core`` ``WARNING``
|
|
|
|
|
``>5*core`` ``CRITICAL``
|
|
|
|
|
============= ============
|
|
|
|
|
|
|
|
|
|
.. note::
|
|
|
|
|
Limit values can be overwritten in the configuration file under
|
|
|
|
|
the ``[load]`` section.
|
|
|
|
|
|
|
|
|
|
.. _load average: http://nosheep.net/story/defining-unix-load-average/
|
2017-06-27 22:13:26 +03:00
|
|
|
.. _load on BSD: http://undeadly.org/cgi?action=article&sid=20090715034920
|
