CMcmrdporcupine·Apr 26, 2026
Monio and Glommio
https://github.com/bytedance/monoio
https://github.com/DataDog/glommio
In What async promised and what it deliveredDataDog
glommio
Rust2020–2026
DataDog / glommio
glommio
Glommio is a thread-per-core crate that makes writing highly parallel asynchronous applications in a thread-per-core architecture easier for rustaceans.
14Distinct people
18Mentions
0Explicit recommenders
3.7KGitHub stars
What to know before exploring
What it is
Glommio is a thread-per-core crate that makes writing highly parallel asynchronous applications in a thread-per-core architecture easier for rustaceans.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- monoio-rs/monoio · linked in 5 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year18 dated mentions
Observed mentions: 2020-09-02 22:20:45 UTC to 2026-04-26 12:04:02 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 4 | 2 | 2 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
18 sourcesglommio is pretty well respected. https://www.datadoghq.com/blog/engineering/introducing-glomm...
https://github.com/DataDog/glommio
ByteDance also has their very fast monio. https://github.com/bytedance/monoio
Both integrate io-uring support for very fast io.
In OpenTelemetry protocol with Apache ArrowI feel a bit paralyzed by Fear Of Missing Io_Uring. There's so much awesome streaming stuff about (RisingWave, Materialize, NATS, DataFusion, Velox, neat upstarts like Iggy, many more), but it all feels built on slower legacy system libraries.
It's not heavily used yet, but Rust has a bunch of fairly high visibility efforts. Situation sort of feels similar with http3, where the problem is figuring out what to pick. https://github.com/tokio-rs/tokio-uring https://github.com/bytedance/monoio https://github.com/DataDog/glommio
Alas libuv (powering Node.js) shipped io_uring but disabled it latter. Seems to have significantly worn out the original author on the topic to boot. https://github.com/libuv/libuv/pull/4421#issuecomment-222586...
In Gazette: Cloud-native millisecond-latency streamingMy understanding is you always need a runtime to play the async game -- something needs to drive the async flow. But there are others on the market, just not without the.. market domination... of tokio.
https://github.com/smol-rs/smol looks promising simply for being minimal
https://github.com/bytedance/monoio looks potentially easier to work with than tokio
https://github.com/DataDog/glommio is built around linux io_uring and seems somewhat promising for performance reasons.
I haven't played with any of these yet, because Tokio is unfortunately the path of least resistance. And a bit viral in how it's infected things.
But I'm planning on giving glommio at least a whirl.
In The State of Async Rust: RuntimesI think you missed one which is based on io_uring [1].
In my benchmarks with a slightly tweaked version it was 2x faster than Nginx and and 30x faster than Python's SimpleHttpServer.
[1] https://github.com/DataDog/glommio/blob/master/examples/hype...
In Learning async Rust with entirely too many web serversYou might be interested in these.
tl;dr People are literally reimplementing tokio (differently) just to avoid this cost.
https://www.youtube.com/watch?v=PbgTyCSDPrs
https://itnext.io/modern-storage-is-plenty-fast-it-is-the-ap...
https://news.ycombinator.com/item?id=25220892
https://github.com/DataDog/glommio
https://www.datadoghq.com/blog/engineering/introducing-glomm...
In Local async executors and why they should be the default> Few of us have really figured out io_uring. But that doesn't mean it is slower.
seastar.io is a high level framework that I believe has "figured out" io_uring, with additional caveats the framework imposes (which is honestly freeing).
Additionally the rust equivalent: https://github.com/DataDog/glommio
In Using io_uring for network I/OIt's worth mentioning: Under "Async Executors", for "io_uring" there is only "Glommio"
I recently found out that ByteDance has a competitor library which supposedly has better performance:
https://github.com/bytedance/monoio
https://github.com/DataDog/glommio/issues/554
In Blessed.rs – An unofficial guide to the Rust ecosystem> I'm working in Rust, not Zig, but a lot of nice stuff to read through here.
FYI, Datadog has a Rust library for scheduling things to run thread-per-core with io_uring
It'd be really useful for DB use cases:
https://github.com/DataDog/glommio
In Building a database buffer pool in Zig using io_uring's new fixed-buffer modeTokio is not a shared-nothing model - you’d be looking at Glommio [1] (from one of the contributors to Seastar) for that.
[1]: https://github.com/DataDog/glommio
In Dragonflydb – A modern replacement for Redis and MemcachedGlommio uses io_uring: https://github.com/DataDog/glommio
And I integrated Hyper as an example:
https://github.com/DataDog/glommio/blob/master/examples/hype...
And the performance was blisteringly quick (6x better latency streaming from a file compared to Nginx).
In Monoio – A thread-per-core Rust async runtime with io_uringThe arch of ScyllaDB blew my mind gotta say. Great talk [1] by Avi Kivity, co-founder of Scylla that goes over the design and architecture.
Glommio [2] (believe it used to be called Scipio) is a thread-per-core framework for Rust modeled after Seastar.
There isn't much in the hn hive mind about it, this one [3] stands out.
[1] https://www.youtube.com/watch?v=0S6i9BmuF8U
[2] https://github.com/DataDog/glommio
[3] https://news.ycombinator.com/item?id=24976533
In Amazon MemoryDB for Redis – A Redis-Compatible, Durable DatabaseGlommio: Cooperative Thread-per-Core crate for Rust and Linux based on io_uring
1 points · Open discussionNice tip, thanks.
Related: The experimental async aware (io_uring optimized) Glommio API may eventually supplant POSIX I/O.
https://github.com/DataDog/glommio
"Modern storage is plenty fast. It is the APIs that are bad." https://itnext.io/modern-storage-is-plenty-fast-it-is-the-ap...
In Linux Kernel: The multi-generational LRUIf anybody's interested, there's a Seastar inspired library for Rust that is being developed https://github.com/DataDog/glommio
In Thread-Per-Core Buffer Management for a modern storage systemShowing the 15 most recent of 18 sources. Enable JavaScript to search and browse every indexed mention.