Thanks for your work on profiling our power management!
> script: power.d/journal-commit
> Recommendation: We remove this script for two reasons:
> 1) It is shown not to save power on a busy system
Ok, but what about on an *idle* system? The premise is that during normal usage (and I don't consider running a package build normal usage), a system on battery should not need to wake up the disk at all more than once every few minutes. I know that on the desktop we appear to have other bugs causing this to not be the case, but I think that does need to remain the goal. If we're not thrashing the disk by doing a package build, does a higher journal commit time help or hinder power savings?
Hi Colin,
Thanks for your work on profiling our power management!
> script: power.d/ journal- commit
> Recommendation: We remove this script for two reasons:
> 1) It is shown not to save power on a busy system
Ok, but what about on an *idle* system? The premise is that during normal usage (and I don't consider running a package build normal usage), a system on battery should not need to wake up the disk at all more than once every few minutes. I know that on the desktop we appear to have other bugs causing this to not be the case, but I think that does need to remain the goal. If we're not thrashing the disk by doing a package build, does a higher journal commit time help or hinder power savings?