In LuCI, under Status >> Realtime Graphs >> Load >> Realtime Load, the graph simply graphs the system load average numbers. Since there is no labeling or explanation here, this is confusing to newcomers. Looking at it for the first time, you might image you were looking at some kind of CPU utilization percentage. But it is actually system load averages which is a somewhat complicated subject when using a Linux kernel. I found this very interesting read here:
"On Linux, load averages are (or try to be) "system load averages", for the system as a whole, measuring the number of threads that are working and waiting to work (CPU, disk, uninterruptible locks). Put differently, it measures the number of threads that aren't completely idle. Advantage: includes demand for different resources."
The ideal if the Realtime Load Graph page had a link pointing back to this issue, or other relevant documentation. If I wasn't at work I'd put together a quick patch.
In LuCI, under Status >> Realtime Graphs >> Load >> Realtime Load, the graph simply graphs the system load average numbers. Since there is no labeling or explanation here, this is confusing to newcomers. Looking at it for the first time, you might image you were looking at some kind of CPU utilization percentage. But it is actually system load averages which is a somewhat complicated subject when using a Linux kernel. I found this very interesting read here:
http://www.brendangregg.com/blog/2017-08-08/linux-load-averages.html
He sums it up by saying:
"On Linux, load averages are (or try to be) "system load averages", for the system as a whole, measuring the number of threads that are working and waiting to work (CPU, disk, uninterruptible locks). Put differently, it measures the number of threads that aren't completely idle. Advantage: includes demand for different resources."
The ideal if the Realtime Load Graph page had a link pointing back to this issue, or other relevant documentation. If I wasn't at work I'd put together a quick patch.
That can't be helped. Adding more to the pile only causes more confusion.
The ideal if the Realtime Load Graph page had a link pointing back to this issue
NO! Luci is already a mess and adding more clutter is not going to help fix anything. Why should my router be calling upon or linking to remote assets? Also, issues are not replacement for documentation and not meant to be permanent.
libreCMC was never meant to be a hand-holding distro and I can't foresee that being true in the future.
>
...this is confusing to newcomers.
That can't be helped. Adding more to the pile only causes more confusion.
>
The ideal if the Realtime Load Graph page had a link pointing back to this issue
NO! Luci is already a mess and adding more clutter is not going to help fix anything. Why should my router be calling upon or linking to remote assets? Also, issues are not replacement for documentation and not meant to be permanent.
libreCMC was never meant to be a hand-holding distro and I can't foresee that being true in the future.
In LuCI, under Status >> Realtime Graphs >> Load >> Realtime Load, the graph simply graphs the system load average numbers. Since there is no labeling or explanation here, this is confusing to newcomers. Looking at it for the first time, you might image you were looking at some kind of CPU utilization percentage. But it is actually system load averages which is a somewhat complicated subject when using a Linux kernel. I found this very interesting read here:
http://www.brendangregg.com/blog/2017-08-08/linux-load-averages.html
He sums it up by saying:
"On Linux, load averages are (or try to be) "system load averages", for the system as a whole, measuring the number of threads that are working and waiting to work (CPU, disk, uninterruptible locks). Put differently, it measures the number of threads that aren't completely idle. Advantage: includes demand for different resources."
The ideal if the Realtime Load Graph page had a link pointing back to this issue, or other relevant documentation. If I wasn't at work I'd put together a quick patch.
That can't be helped. Adding more to the pile only causes more confusion.
NO! Luci is already a mess and adding more clutter is not going to help fix anything. Why should my router be calling upon or linking to remote assets? Also, issues are not replacement for documentation and not meant to be permanent.
libreCMC was never meant to be a hand-holding distro and I can't foresee that being true in the future.
Okay.