View Single Post
Framstag's Avatar
Posts: 72 | Thanked: 51 times | Joined on Jul 2008 @ Germany
#11
Originally Posted by qgil View Post
There must be a way to discern intended from buggy compromises in performance.

One thing is when one app of dedicated use takes a lot of CPU to perform an action understood and desired by the user (render a 3D graph) and another is to have some widget scrolling in such a buggy way that the system becomes sluggish.

And no matter what, Octave just paused in some inactive window should let the system work as usual, 5 minutes same as 5 days after booting the program.
While I do not question in anyway the requiremnt to prevent uncessary power consumption, I also have the feeling to the power consumption criteria needs a more detailed and precise formulation.

DiskUsage for example polls file system size around every 5 seconds and also does graphical refreshes. I assume that this should be avoided if the application is not active and thus can be seen as blocker. From the developer view however I need a clear definition of "active" in this case. I remember a discussion exactly about this topic in the developer mailing list. I havn't yet time to check if there is now a documentation about that (that does not focus on use Gtk and it will make it right) that possibly should even be linked in this case.

WifiInfo on the other hand also polls network information in the background. user feedback for the N810 showed that battery will last around 2-3 hours in such mode, so polling should be avoided for a deactive application, too, and current behaviour is likely a blocker, too. On the other hand there is a new wardriving mode, that creates sounds if a open network is detected and it is intended to have this on even while the application is not active. So battery drain is a also intended consequence. I hope this will not stop the application from getting into extras in future. I also have no problem to warn the user once about this mode using a module dialog or similar. I just would like to have a clearification of such handling before I upload it to extras-testing and get lost in various upload iterations and discussions :-)

Since power management is a very difficult topic also for the devloper I would suggest to add as much cross reference regarding testing on my own and technical solutions to definition of "active" and similar, perhaps build a wiki page on its own for this topic (which did not exist the last time I looked).

Gruß...Tim

Last edited by Framstag; 2009-10-23 at 12:05.