Hi, Gary Birkett wrote: > would it be wise to document all the best practices in one place though?
Best practices, and tools you can use to identify, characterise and fix power issues. This has at least 3 different facades: * Do less stuff - Use the right algorithms - Don't do things you don't have to - Don't poll needlessly * Work smarter - Handle events asynchronously - Be aware of trade-off between pre-calculating and working on-demand * Have a tuned system - All the stuff powertop can find - allow devices & system components to switch off/suspend when not in use, increase buffering & writeback time, etc, etc The third one is the black magic stuff that I don't understand (and the only one addressed by lesswatts.org apparently). I do know that there's not much that an application developer can do at that level to ensure their app behaves well, but we can certainly ensure that apps are doing less and behaving correctly as good citizens when handling user interaction, wake-ups, signals, handling I/O, etc. I'd appreciate someone putting a guide together for those types of issues personally. > also for applications to be well behaved, they should know something > about their environment > to that end should know where to look for the charging status for instance > if the devices have a power profile available, the api to access this > should be documented and clearly stated > I believe that sort of information is what Narendranath Ghosh was requesting. Good point - it would be great to know when you're on battery, and do even less. Cheers, Dave. -- maemo.org docsmaster Email: [email protected] Jabber: [email protected] _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
