High-Performance DBMSs with io_uring: When and How to use it
1–10 of 50 posts
Re: High-Performance DBMSs with io_uring: When and How to use it
#2Hi, I am one of the authors. Happy to take questions.
Re: High-Performance DBMSs with io_uring: When and How to use it
#3This is one of the most easy-to-follow papers on io_uring and its benefits. Good work!
Re: High-Performance DBMSs with io_uring: When and How to use it
#4We also wrote up a very concise, high-level summary here, if you want the short version: https://toziegler.github.io/2025-12-08-io-uring/
Re: High-Performance DBMSs with io_uring: When and How to use it
#5We also wrote up a very concise, high-level summary here, if you want the short version: https://toziegler.github.io/2025-12-08-io-uring/
Thanks! This explained to me very simply what the benefits are in a way no article I’ve read before has.
Re: High-Performance DBMSs with io_uring: When and How to use it
#6We also wrote up a very concise, high-level summary here, if you want the short version: https://toziegler.github.io/2025-12-08-io-uring/
Thanks! This explained to me very simply what the benefits are in a way no article I’ve read before has.
That’s great to hear! We are happy it helped.
Re: High-Performance DBMSs with io_uring: When and How to use it
#7We also wrote up a very concise, high-level summary here, if you want the short version: https://toziegler.github.io/2025-12-08-io-uring/
In your high level "You might not want to use it if" points, you mention Docker but not why, and that's odd. I happen to know why: io_uring syscalls are blocked by default in Docker, because io_uring is a large surface area for attacks, and this has proven to be a real problem in practice. Others won't know this, however. They also won't know that io_uring is similarly blocked in widely used cloud sandboxes, Android, and elsewhere. Seems like a fine place to point this stuff out: anyone considering io_uring would want to know about these issues.
Re: High-Performance DBMSs with io_uring: When and How to use it
#8Small nitpick: malloc is not a system call.
Re: High-Performance DBMSs with io_uring: When and How to use it
#9We also wrote up a very concise, high-level summary here, if you want the short version: https://toziegler.github.io/2025-12-08-io-uring/
In your high level "You might not want to use it if" points, you mention Docker but not why, and that's odd. I happen to know why: io_uring syscalls are blocked by default in Docker, because io_uring is a large surface area for attacks, and this has proven to be a real problem in practice. Others won't know this, however. They also won't know that io_uring is similarly blocked in widely used cloud sandboxes, Android,…
Very good point! You’re absolutely right: The fact that io_uring is blocked by default in Docker and other sandboxes due to security concerns is important context, and we should have mentioned it explicitly there. We'll update the post, and happy to incorporate any other caveats you think are worth calling out.
Re: High-Performance DBMSs with io_uring: When and How to use it
#10Small nitpick: malloc is not a system call.
Good catch! We will fix this in the next version and change it to brk/sbrk or mmap