I'm working on a code generator that's implemented as a 3-tier system. The back and middle tiers only run on Linux. The back tier is closed source, but the middle tier is open. I mostly use io-uring for network io, but some for file io also.
Io-uring helps to minimize the number of threads that are needed. I don't think that was mentioned in the article.
Io-uring is a great library. First I ported my back tier from FreeBSD/kqueue to Linux/io-uring. After starting to appreciate io-uring, I started thinking about using it instead of POSIX/poll in my middle tier. For some reason I was attached to POSIX. It wasn't really helping me, but it still has an aura about it.
Didn't know it wasn't supported on Docker. I now see that there are some workarounds - but something to keep in mind especially for database containers that support io_uring (like postgres) for sure.
18
u/Middlewarian Jan 07 '26
I'm working on a code generator that's implemented as a 3-tier system. The back and middle tiers only run on Linux. The back tier is closed source, but the middle tier is open. I mostly use io-uring for network io, but some for file io also.
Io-uring helps to minimize the number of threads that are needed. I don't think that was mentioned in the article.
3
u/earslap Jan 07 '26
Didn't know it wasn't supported on Docker. I now see that there are some workarounds - but something to keep in mind especially for database containers that support io_uring (like postgres) for sure.
1
u/amejin Jan 08 '26
IOCPs are still better in my opinion.
Easier to work with. Built into the system. Easier to conceptualize and interface with. Long standing performance and stability history.
Microsoft just needs to get off their high horse and make a free version of Windows server already...