Who is this for?
Built specifically for systems teams where generic abstraction layers cost too much CPU time and introduce unacceptable tail latency.
Engineers building high-throughput database write-ahead logs (WAL), time-series stores, and message queues.
C++ developers seeking deterministic sub-millisecond p99 storage latency on Linux.
Teams that need the raw performance of io_uring without managing low-level kernel ring structs and buffer registration manually.
What problem does it solve?
Eliminates blocking thread stalls, context switches, and ring allocation overhead.
Standard POSIX pread/pwrite blocks the calling thread, forcing applications into large thread pools that degrade cache locality and spike tail latency. While raw liburing allows async batching, it requires manual synchronization and error-prone buffer lifetimes. FluxIO provides an ergonomic, zero-hot-path-allocation C++20 abstraction with true zero-syscall kernel SQPOLL submission.
Why choose FluxIO instead of existing alternatives?
How FluxIO compares with standard Linux approaches on latency, safety, and operational overhead.
| Approach / Technology | Verdict | Trade-off & Limitation |
|---|---|---|
| POSIX read / write | Blocking & Jitter-Prone | Each read/write incurs a kernel context switch; thread pools cause heavy cache bouncing. |
| Boost.Asio File I/O | Thread-Pool Simulation | Historically delegates file I/O to background OS threads rather than native kernel async rings. |
| Raw liburing (C) | Manual & Unsafe | Exposes raw C structs, no compile-time safety, manual SQE/CQE ring management. |
| FluxIO (AlgoMesh) | Zero-Syscall C++20 | Header-only, pre-registered fixed buffers, kernel SQPOLL, and automatic direct I/O fallback. |
Key Capabilities
Get started
Add to a CMake project
include(FetchContent)
FetchContent_Declare(
fluxio
GIT_REPOSITORY https://github.com/programmingGod-byte/FluxIO.git
GIT_TAG main
)
FetchContent_MakeAvailable(fluxio)
target_link_libraries(my_app PRIVATE FluxIO::fluxio)On the roadmap
What is planned next. Follow progress on GitHub.
- Ordered, durable fsync (IOSQE_IO_DRAIN / linked requests)
- Asynchronous preallocation off the hot path
- fio baseline comparisons and a sanitizer-backed test suite