View Single Post
Posts: 262 | Thanked: 9 times | Joined on Jun 2007
#23
Originally Posted by Milhouse View Post
trevarthan - kagu.py consumes 15-25% CPU even when the UI is inactive, is this the pygame main thread issue you touched on in a previous thread?
Yes. PyGame is intended for games, not applications. It's a bit of a hog. Normally, it uses 100% CPU, so at least we've got it down to 20%. BTW, UKMP and Canola have the same issue as they both use PyGame.

Originally Posted by Milhouse View Post
If Kagu is minimised, kagu.py doesn't appear to use any significant amount of CPU but when Kagu is the active/focused application the UI uses far too much CPU when idle. And when audio is being played (a2dp or otherwise) the UI continues to consume CPU cycles at the rate of 15-25%.

Is there any way to eliminate this UI CPU consumption when Kagu is active/focused?
Turning off the screen (Power button then center dpad button is a quick way to do this) also forces Kagu into low CPU mode. UKMP doesn't do this yet, but I talked to Konttori just this morning about it and he seemed interested in Kagu's code for doing this.

We can't really reduce the normal (i.e. screen state = on) CPU usage any further without increasing screen response latency. What does that mean? It means that if we increase CPU savings, then it'll take longer for Kagu's scroll widget to respond when you try to interact with it.

We should probably allow the user to tune this value from kagu-scanner or gconf. I've opened a ticket to remind us to do that in the future: https://www.guardiani.us/projects/kagu/ticket/28