* I have many VMs in my computer. * I use i3 with qubes-i3status * The script qubes-i3status calls command qvm-ls --no-spinner --raw-data --fields NAME,FLAGS quite frequently. * The command qvm-ls --no-spinner --raw-data --fields NAME,FLAGS seems to cause high CPU load. Unfortunately, the process that shows the high CPU usage is qubesd, not qvm-ls.What can be improved: a. Don't use qubes-i3status. Problem solved. b. Optimize qvm-ls. Not sure how hard it is.
This issue is really old (back from at least 3.2) and caused by each qvm-ls line relating to one request to qubesd. Actually it was even worse with 3.2. It should improve with 4.1 though, see .  https://github.com/QubesOS/qubes-issues/issues/3293
c. Optimize qubes-i3status. I am not sure about the ideal way of doing that, but clearly running qvm-ls --no-spinner --raw-data --fields NAME,FLAGS just to compute the number of running qubes is far from optimal. One could add --running. And maybe it could have been written without flags. The script just ignores VMs with the first flag being “0” (maybe in order to ignore dom0) and the second flag being “r” (probably not needed with --running).
Filtering might work in the meantime, yes. BR David -- 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/e8acbeda-199a-8e1f-1a94-caaa0b4bb120%40hackingthe.net.
Description: S/MIME Cryptographic Signature