The battery time can be much more if dash doesn't write to dconf if each opening. Reading is OK, becaouse after the first read, the cache will store it, but after each writeing, dconf do a sync. So I do a sync after each dash opening.
If my programs loaded, (and X, unity, etc) I mainly don't need to use the hdd. (For example Firefox not use hdd if I just search the web. The content cache is automatically written into the memory if it's enough and the hdd is not in use) If I can turn off, (spin down) the hdd, it will much improve my work time on battery. So it _will_ improve work time on battery. BUT I can't spin down my hdd becaouse dash synces small stupid things to the disc on each opening. I don't know why dconf sync everything immediatly, but becaouse it does it, dash should only write values to dconf if they are modifyed. (Just note: I don't know why we use dconf instead of gconf, which is used the memory, and not synced immediately. It was better for battery time, and for speed too. I hope this change wasn't stupid.) If you don't think it's problem, I can agree with you, but in fact, that's why windows 7 can run more from battery: It spins down the hdd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/793156 Title: Dash writes to dconf when not necessary To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/793156/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
