https://bugs.kde.org/show_bug.cgi?id=497341
Arjen Hiemstra <ahiems...@heimr.nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|REPORTED |CONFIRMED
--- Comment #6 from Arjen Hiemstra <ahiems...@heimr.nl> ---
The CPU usage values are computed by reading `/proc/stat` which contains the
amount of time the different cores have been in different states. We divide
these values into three groups: system, user and wait and calculate the
percentages of these. The total CPU usage percentage is then these three added
together.
Now, one of the values in "wait" is "iowait" which is the amount of time spent
idle but while some process is waiting on IO. Now, I don't know what GhostTTY
is doing but the end result is that it's causing almost 100% iowait on a core.
This then results in the total usage sensor reporting 100% usage.
While we should probably remove iowait from the CPU usage accounting (as it is
not actually doing anything), there *also* seems to be a problem in GhosTTY,
other processes don't cause this much iowait.
Note that this is actually also visible in top, the "%wa" statistic at the top
shows ~16% for my machine when ghostty is running.
--
You are receiving this mail because:
You are watching all bug changes.
