Linux / proc / loadavg

When issuing this command from linux:

# cat /proc/loadavg 0.75 0.35 0.25 1/25 1747 

What are the last 2 numbers?

The last time is increasing by 2 every second, should I worry?

+66
linux
Aug 16 2018-12-12T00:
source share
3 answers

The last is the system workload in the last 15 minutes.

/ proc / loadavg

The first three fields in this file are the average load values ​​giving the number of jobs in the execution queue (state R) or the I / O disk wait (state D) is averaged over 1, 5, and 15 minutes . They are the same as the average load values ​​determined by the uptime (1) and other programs.

The fourth field consists of two numbers separated by a slash (/). The first of these is the number of currently running kernel scheduling objects (processes, threads); it will be less than or equal to the number of processors. The value after the slash is the number of kernel planning objects that currently exist on the system.

The fifth field is the PID of the process that was most recently created in the system.

+76
Aug 16 2018-12-12T00:
source share

The first three columns measure CPU and I / O utilization for the last, five, and 15 minute periods. The fourth column shows the number of processes currently running and the total number of processes. The last column displays the most recently used process identifier.

https://docs.fedoraproject.org/en-US/Fedora/17/html/System_Administrators_Guide/s2-proc-loadavg.html

+14
Aug 16 2018-12-12T00:
source share

I would like to comment on the accepted answer.

The fourth field consists of two numbers separated by a slash (/). the first of them is the number of currently executing kernel graphs of objects (processes, threads); it will be less than or equal to the number of processors.

I ran a test program that reads an integer N from input and then creates N threads and starts them forever. On an RHEL 6.5 computer, I have 8 processors, and each processor has hyperthreading. In any case, if I run my test and it creates 128 threads, I see in the fourth field values ​​exceeding 128, for example 135. This is clearly more than the number of CPUs. This post supports my observations: http://juliano.info/en/Blog:Memory_Leak/Understanding_the_Linux_load_average

It is worth noting that the current explanation on the proc (5) manual page (from the man pages of version 3.21, March 2009) is incorrect. It reports the first number of the fourth field as the number of objects that are currently being planned, and therefore predicts that it cannot be greater than the number of processors. This does not match the actual implementation when this value reports the current number of threads running.

+13
Feb 07 '14 at 6:43
source share



All Articles