Conversation
A higher file system commit interval can help to decrease the amount of writes. In tests, a commit interval of higher than 30s seems not to help much in practice. Settle with 30s for now.
|
It seems like big distributions like Ubuntu leave it as default. But those are also geared towards desktop type systems, so might not be a good indicator. ArchLinux has it as a "performance improvement" tip set to 60s in the example. Debian Wiki has a tip to set to 600s. ChromeOS synchronizes it with All in all, I expect this to create a bit more issues where files get corrupted (like the key.json corruption we are seeing, see #1706). But in the end those are software bugs which should be fixed (either the software needs to use a save write mechanism, or handle empty files properly). |
|
Let's test the 30s. I'm more worry about docker layers |
ext4 filesystem will not use a default of 1s. (cf. home-assistant/operating-system#2103)
A higher file system commit interval can help to decrease the amount of
writes. In tests, a commit interval of higher than 30s seems not to help
much in practice. Settle with 30s for now.
Some tests about this change can be found here:
https://community.home-assistant.io/t/researching-i-o-write-improvements/456227