DConf should not fsync for some keys
Submitted by Jonathan Briggs
Assigned to dco..@..e.bugs
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.