From fb31765cbe33890f325a87015507364156741321 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sun, 7 Apr 2024 19:59:44 +0200 Subject: Adding upstream version 42.0. Signed-off-by: Daniel Baumann --- help/C/process-loadaverage.page.stub | 50 ++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 help/C/process-loadaverage.page.stub (limited to 'help/C/process-loadaverage.page.stub') diff --git a/help/C/process-loadaverage.page.stub b/help/C/process-loadaverage.page.stub new file mode 100644 index 0000000..6b21b9a --- /dev/null +++ b/help/C/process-loadaverage.page.stub @@ -0,0 +1,50 @@ + + + + + + + Phil Bull + philbull@gmail.com + 2011 + + + + Michael Hill + mdhillca@gmail.com + 2011 + + + The load average tells you how much work your computer has + been doing over the past few minutes. + + + What is the load average? + + + Phil Bull +

Explain how to interpret the load averages quoted on the Processes tab.

+
+ +

The load average shows the load on the CPU over three different + time intervals, one minute, five minutes and fifteen minutes. These are displayed + on the Processes tab above the process list, and are an indicator of + system processing capacity.

+ +

The load is the number of processes currently running plus the + number of processes queued to run on the system's CPU(s). A load + showing a utilization of 100% would be roughly 1.0 times the number of CPUs or + cores in the system; load averages constantly + hitting this number would indicate that the system is fully-loaded with no + processes waiting for processor time. Lower numbers indicate that the system's + processing power is sufficient for the processes being run, while numbers that + are consistently higher might mean more processing power is needed.

+ +

Three intervals are shown so that spikes and trends in the numbers can be + taken into account: if the load average spikes higher in the one- or + five-minute intervals, but settles down below the 100% mark over the + fifteen-minute interval, system processing capacity is probably sufficient.

+ +
-- cgit v1.2.3