Different I/O Access Methods for Linux, What We Chose for ScyllaDB, and WhyDate: May 18, 202210:00AM PDT (UTC-7)
Join Us for a Complimentary Live Webinar
Sponsored by ScyllaDB
When most server application developers think of I/O, they consider network I/O since most resources these days are accessed over the network: databases, object storage, and other microservices. However, the developer of a database must also consider file I/O.
This webinar provides a detailed technical overview of the available choices for I/O access and their various tradeoffs. We then explain why ScyllaDB chose asynchronous direct I/O (AIO/DIO) as the access method for our high-performance low latency database and review how that decision has impacted our engineering efforts as well as our product performance.
We will cover:
- Four choices for accessing files on a Linux server: read/write, mmap, Direct I/O (DIO) read/write, and asynchronous direct I/O (AIO/DIO)
- The tradeoffs among these choices with respect to core characteristics such as cache control, copying, MMU activity, and I/O scheduling
- Why we chose AIO/DIO for ScyllaDB and a retrospective on that decision seven years later
Avi Kivity, CTO, ScyllaDB
Avi Kivity is known mostly for starting the Kernel-based Virtual Machine (KVM) project, the hypervisor underlying many production clouds. He worked for Qumranet and Red Hat as a KVM maintainer until December 2012. Avi is now CTO of ScyllaDB, bringing high throughput to the NoSQL world.