OK, reported, some optimization attempts included: https://groups.google.com/g/qubes-users/c/uTi3QHuhdy8
Also, I have some temptation to reimplement qubes-i3status as a Python wrapper around the original i3status. We would probably also resolve some other problems. For example, I had to fix reading of the battery status. BTW, if you have ~25% CPU load, I guess you just have quad-core CPU (or maybe dual-core with hyperthreading). Regards, Vít Šesták 'v6ak' On Wednesday, January 6, 2021 at 11:34:42 AM UTC+1 Jarrah wrote: > This is some really nice tracing work. I'm sure it would be appreciated > as an issue in the qubes-issues repository so it can be tracked properly. > > While I haven't gone to the same depth, I can confirm that `qubesd` > jumps to ~25% CPU regularly on my (albeit much beefier) system with i3. > This does correlate with qubes-i3status running on my system as well. > > > As a temporary work around, you could modify the script > (/usr/bin/qubes-i3status:123) to run every minute or longer. This would > have the downside of the clock updating slower, but otherwise should not > be a problem. > > Alternatively, if the number of running VMs doesn't interest you, you > could comment out line 113 and modify 122 to suit this. > > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e3bcfe4b-2127-4d94-a3d0-07871ffbaf37n%40googlegroups.com.