This is an automated email from the ASF dual-hosted git repository.
gkoszyk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/iggy-website.git
The following commit(s) were added to refs/heads/main by this push:
new 418cade1 fix typo
418cade1 is described below
commit 418cade19951b38bf75cbecae527784ac7432331
Author: numinex <[email protected]>
AuthorDate: Fri Feb 27 11:12:16 2026 +0100
fix typo
---
content/blog/thread-per-core-io_uring.mdx | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/content/blog/thread-per-core-io_uring.mdx
b/content/blog/thread-per-core-io_uring.mdx
index b9ed6581..6fe000c7 100644
--- a/content/blog/thread-per-core-io_uring.mdx
+++ b/content/blog/thread-per-core-io_uring.mdx
@@ -35,7 +35,8 @@ With all the design pieces in place, it was time to visit the
marketplace of **a
- `compio`
All of them support `io_uring` as the driver, some exclusively, others as one
of several available ones.
-,
+
+
Using the FIFO order - [monoio](https://github.com/bytedance/monoio) was our
choice for the initial
[proof-of-concept](https://github.com/apache/iggy/tree/io_uring_monoio_runtime),
it worked pretty well, but as we explored the monstrous API surface of
`io_uring`, we realized that it's pretty far behind when it comes to feature
parity and doesn't appear to be very actively maintained. Don't get us wrong,
the runtime still receives patches, especially after [incidents like
this](https://ww [...]
Next on the list [glommio](https://github.com/DataDog/glommio) - this one is
particularly interesting as it was initially developed by `Glauber Costa`, who
previously worked at `ScyllaDB`, the creators of the `Seastar` framework,
`glommio` significantly differs from the other two runtimes on our list. It's
still a thread-per-core runtime, but it uses a proportional-share scheduler,
creates 3 `io_uring` instances per thread (a main ring, a latency ring, and a
polling ring), and ships with [...]
