Hi @Exadra37 , thanks for your observation. CubDB does not use delayed writes, so when setting auto_file_sync: true a file sync is programmatically triggered at the end of each transaction. As you noted, this strong durability guarantee comes at a performance cost. Setting auto_file_sync: false conversely trades durability for performance.
When persisting configuration, it makes sense to keep durability, as performance won’t be a problem with sporadic writes. When using CubDB for data logging, or other high volume write use case, it might make sense to choose performance instead.
the responsibility of ensuring durability and avoiding corruption at the low level ultimately resides with the file system and disk controller.