Load (computing) - Wikipedia: In UNIX computing, the system load is a measure of the amount of computational work that a computer system performs. The load average represents the average system load over a period of time. It conventionally appears in the form of three numbers which represent the system load during the last one-, five-, and fifteen-minute periods.
All Unix and Unix-like systems generate a dimensionless metric of three "load average" numbers in the kernel. Users can easily query the current result from a Unix shell by running the uptime command:
The w and top commands show the same three load average numbers, as do a range of graphical user interface utilities. In GNU/Linux, they can also be accessed by reading the
An idle computer has a load number of 0 (the idle process isn't counted). Each process using or waiting for CPU (the ready queue or run queue)
increments the load number by 1. Each process that terminates
decrements it by 1. Most UNIX systems count only processes in the running (on CPU) or runnable (waiting for CPU) states.
However, Linux also includes processes in uninterruptible sleep states (usually waiting for disk activity), which can lead to markedly different results if many processes remain blocked in I/O due to a busy or stalled I/O system.[1] This, for example, includes processes blocking due to an NFS server failure or too slow media (e.g., USB
1.x storage devices).
Such circumstances can result in an elevated load
average which does not reflect an actual increase in CPU use (but still
gives an idea of how long users have to wait).
All Unix and Unix-like systems generate a dimensionless metric of three "load average" numbers in the kernel. Users can easily query the current result from a Unix shell by running the uptime command:
$ uptime
14:34:03 up 10:43, 4 users, load average: 0.06, 0.11, 0.09 /proc/loadavg file.An idle computer has a load number of 0 (the idle process isn't counted). Each process using or waiting for CPU (the ready queue or run queue)
increments the load number by 1. Each process that terminates
decrements it by 1. Most UNIX systems count only processes in the running (on CPU) or runnable (waiting for CPU) states.
However, Linux also includes processes in uninterruptible sleep states (usually waiting for disk activity), which can lead to markedly different results if many processes remain blocked in I/O due to a busy or stalled I/O system.[1] This, for example, includes processes blocking due to an NFS server failure or too slow media (e.g., USB
1.x storage devices).
Such circumstances can result in an elevated load
average which does not reflect an actual increase in CPU use (but still
gives an idea of how long users have to wait).
Hello, my name is Jack Sparrow. I'm a 50 year old self-employed Pirate from the Caribbean.
No comments:
Post a Comment