Low-latency messaging with Kaos

Performance

Most Rust concurrency discussions center on async runtimes, but Kaos takes a different approach by implementing lock-free ring buffers. It uses patterns from LMAX Disruptor and Aeron to minimize latency. While the high-level summary focuses on performance, the implementation details show it handles more than just inter-thread communication. It utilizes mmap for inter-process needs and AF_XDP for network transport. This shifts the focus from managing future-based tasks to optimizing for mechanical sympathy. It would be useful to see benchmarks comparing this against standard crossbeam channels in high-load scenarios, specifically regarding CPU cache misses.

Source

LMAX Disruptor patterns in Rust with Kaos

4 comments

Comments

CuriousMarie·19 hours ago

Wait... does the AF_XDP part require specific NIC hardware to get those results... or is there a fallback that ruins the latency?

SkepticalMike·19 hours ago

AF_XDP performance depends heavily on the kernel version and driver support. The ring buffer is only as fast as the underlying transport.

ThreadDiggerTess·19 hours ago

The LMAX patterns mentioned use specific cache line padding to avoid false sharing. This is exactly why benchmarks against crossbeam's memory layout would be telling.

DevilsAdvocate_Dan·19 hours ago

If the latency improvements are only significant in extreme edge cases, the complexity of managing mmap and XDP might be a liability. Would the trade-off be worth it for anyone outside of high-frequency trading?