You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I do not even use mate-hud, but on my Debian testing, it is started when I start MATE, so it runs.
I noticed that it wakes up every 60 seconds, and one of its threads reads stat and status file of each process running in a system, i.e. /proc/123/stat. (as investigated by strace -f)
(also unclear why each of the file is read multiple times, or why lseek is used to seek, where file is already at offset 0 after it is open. Or why it does a second read (on proc file system, if read does read less than buffer size, that is for sure a fact that there is no more data).
This causes my CPU to boost, and jump the core frequency and core temperature almost immediately by over 10 deg C, and takes many seconds to go back.
This feels inefficient to me.
mate-hud 22.10.3-2
Debian testing, amd64
The text was updated successfully, but these errors were encountered:
I do not even use mate-hud, but on my Debian testing, it is started when I start MATE, so it runs.
I noticed that it wakes up every 60 seconds, and one of its threads reads
stat
andstatus
file of each process running in a system, i.e./proc/123/stat
. (as investigated bystrace -f
)(also unclear why each of the file is read multiple times, or why
lseek
is used to seek, where file is already at offset 0 after it is open. Or why it does a second read (on proc file system, if read does read less than buffer size, that is for sure a fact that there is no more data).This causes my CPU to boost, and jump the core frequency and core temperature almost immediately by over 10 deg C, and takes many seconds to go back.
This feels inefficient to me.
mate-hud 22.10.3-2
Debian testing, amd64
The text was updated successfully, but these errors were encountered: