The performance load metrics in the context of a system. This CPU metrics is often called a CPU Load average but this is really a system load average as Unix refers it as the run-queue length. Ie:
CPU load can be compared with car traffic. “Cars” are processes:
For one core:
To not wait, the CPU load should ideally stay below 1.00.
Rule of Thumb: 0.70 If your load average is staying above > 0.70, it's time to investigate before things get worse.
On multi-processor system, the load is relative to the number of processor cores available. A load of 1.00 is 100% CPU utilization on single-core box. On a dual-core box, a load of 2.00 is 100% CPU utilization.
The total number of cores is what matters, regardless of how many physical processors those cores are spread across.
grep 'model name' /proc/cpuinfo | wc -l
40
# The max load is then 40
CPU On linux (Uptime and top):
# uptime or top output
12:54:11 up 326 days, 10:56, 1 user, load average: 0.11, 0.08, 0.09
where
The most common technic to decrease the load of a server is to cache the response. 1) 2) 3) 4)