zzsheng
Re:Removing fsync from our local storage engine
on Wednesday May 13, 2026 @09:23AM (#48121591)
we manage memory instead of relying on page cache
Re:Removing fsync from our local storage engine
on Sunday May 10, 2026 @07:41AM (#48083123)
sorry, typo. data will *not* be lost.
Re:Removing fsync from our local storage engine
on Saturday May 09, 2026 @08:37PM (#48079800)
check s3 express one zone
Re:Removing fsync from our local storage engine
on Saturday May 09, 2026 @08:36PM (#48079794)
journal file was pre-alloacated and we use direct-io for journal write so no need to call fsync.
Re:Removing fsync from our local storage engine
on Saturday May 09, 2026 @07:46PM (#48079477)
nop. we will not ack any write which is not in data or journal. please check the put details in the blog.
Re:Removing fsync from our local storage engine
on Saturday May 09, 2026 @07:45PM (#48079465)
actually both crash consistentcy and durability. after we ack, we make sure data will be lost due to crash, restart or power loss.
Re:Removing fsync from our local storage engine
on Saturday May 09, 2026 @07:38PM (#48079412)
we also use direct-io for reads.
Re:Removing fsync from our local storage engine
on Saturday May 09, 2026 @06:20PM (#48078850)
thanks for feedback. actually it was pointed out in blog that we do not use append only log to avoid fsync due to size change. what we use is preallocate fixed size log file and we do write journal data and space reclaim by 4KB unit, also with direct-io.
Re:Removing fsync from our local storage engine
on Thursday May 07, 2026 @05:25AM (#48047281)
Author here. This is not a general argument against fsync; the design depends on SSD-only deployment, preallocated files, O_DIRECT, single-key atomicity, and device write guarantees.