GNOME Bugzilla – Bug 686001
DConf should not fsync for some keys
Last modified: 2018-09-21 16:12:37 UTC
Some dconf keys are so utterly trivial and yet written so often that they should never sync to disk. Especially on laptops. Especially on laptops that are trying to keep the disk spun down for power savings. One example is the key that stores the num-lock state. This is a very trivial setting that no one sane would care about if it got lost. (And I'm shocked anyone even thought this was something useful to record!) And yet, anyone who types with occasional use of caps-lock (and why does caps-lock trigger writing the num-lock state?) will be forcing a drive spin-up just to record that fact. So I propose some method to mark DConf keys with an importance or persistence value. Important data would be synced with disk. Unimportant data would be left in RAM or written without sync.
Would be good to fix the issue of numlock state being updated when you press capslock...
This is unlikely to be fixed any time soon but it gets talked about enough that I have to wonder if maybe it would be nice to eventually address it. I'll leave it open for that reason....
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/dconf/issues/8.