Hacker News Reader

> batching multiple transactions into IO blocks where feasible. If your average transaction is substantially smaller than the IO block size, then you are probably leaving a lot of throughput on the table.

Could you expand on this? A quick Google search didn't help. Link to an article or a brief explanation would be nice!

View on HN

Sure. If you are using some micro-batched event processing abstraction, such as the LMAX Disruptor, you have an opportunity to take small batches of transactions and process them as a single unit to disk.

For event sourcing applications, multiple transactions can be coalesced into a single IO block & operation without much drama using this technique.

Surprisingly, this technique also lowers the amount of latency that any given user should experience, despite the fact that you are "blocking" multiple users to take advantage of small batching effects.

Reply on news.ycombinator.com