I recently read this stack overflow post which was interesting: https://stackoverflow.com/questions/75697877/why-is-liburing-write-performance-lower-than-expec

I recently read this stack overflow post which was interesting: https://stackoverflow.com/questions/75697877/why-is-liburing-write-performance-lower-than-expected https://stackoverflow.com/questions/75697877/why-is-liburing... If you use uring (such as via liburing) on Linux it forces you to split your IO in half: submit and then wait for callback but you can still do other things. You can submit multiple writes or reads in parallel and handle them when they're ready. This white paper talks about writing to disk in S3 in a scheduled order to avoid corruption of concurrent requests in the event of a crash. "Using Lightweight Formal Methods to Validate a Key-Value Storage Node in Amazon S3" Apache Kafka supposedly doesn't need fsync due to the recovery protocol. So you might want to investigate why that is the case and whether or not you can create the same behaviour.