Views:
1,300
Votes: 5
Tags:
hard-drive
ssd
sata
optical
conky
Link:
🔍 See Original Answer on Ask Ubuntu ⧉ 🔗
URL:
https://askubuntu.com/q/1157252
Title:
Load average is high after adding second drive
ID:
/2019/07/10/Load-average-is-high-after-adding-second-drive
Created:
July 10, 2019
Edited: July 10, 2019
Upload:
September 15, 2024
Layout: post
TOC:
false
Navigation: false
Copy to clipboard: false
There is an excellent Q&A with the same problem:
The solution from top-voted answer was this command:
echo "disable" > /sys/firmware/acpi/interrupts/gpe6F
In the link grep was used to discover the interrupt causing grief:
grep . -r /sys/firmware/acpi/interrupts/
Load Average
If you look at your system load average for 1-5-15 minutes like this:
$ cat /proc/loadavg
0.50 0.76 0.91 2/1037 14366
It’s reporting .5, .76 and .91. From Understanding Linux CPU Load - when should you be worried? it says:
- The “Need to Look into it” Rule of Thumb: 0.70 If your load average is staying above > 0.70, it’s time to investigate before
things get worse.
Further in the article it will mention something like the load average for all your CPUs are added together but not divided by the number of CPUs to get an average of all CPUs. You have to do this manually so the true values are:
.063 - .095 - .113
because I have 8 CPUs.
I prefer to use Conky to display this in real-time though:
Notice the 4th line from the bottom display 1-5-15 minute load averages as:
.150 .177 .143
The 1 minute load average of .15 equates to 15% which matches the All CPU percentage value two lines above the Load Average.
Without diving by 8 I’d have a heart attack because I would be seeing:
1.200 1.416 1.144
Conky automatically divides for me with the Conky code:
${execpi .001 (awk '{printf "%s/", $1}' /proc/loadavg; grep -c processor /proc/cpuinfo;) | bc -l | cut -c1-4} ${execpi .001 (awk '{printf "%s/", $2}' /proc/loadavg; grep -c processor /proc/cpuinfo;) | bc -l | cut -c1-4} ${execpi .001 (awk '{printf "%s/", $3}' /proc/loadavg; grep -c processor /proc/cpuinfo;) | bc -l | cut -c1-4}
Of course not everyone uses conky probably only 1% of Linux users but for those out there that love Conky like me, you might find this code helpful.