monoio-rs/monoio

Health v2 · maintenance only

Adoption not part of the score

5081 stars · 295 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

Monoio is a thread-per-core asynchronous Rust runtime built on io_uring (with epoll/kqueue fallbacks), originally developed at ByteDance. Unlike Tokio-uring, it runs standalone rather than atop another runtime, and its thread-per-core model removes the need for Send/Sync bounds on tasks.

Use cases

• build a high-performance network server in Rust
• write a load balancer like NGINX with thread-per-core architecture
• maximize throughput for io-bound socket workloads
• avoid Send/Sync constraints on async tasks
• use io_uring for native async I/O on Linux

When to choose

• you are building io-bound network servers on Linux with kernel 5.6+
• you want thread-per-core semantics and thread-local data without sharing across threads
• you need better performance than Tokio for your specific server workloads

When to avoid

• you need a general-purpose runtime with work-stealing and cross-thread task migration
• you require broad ecosystem compatibility with Tokio-based crates
• your target platform lacks io_uring and you need Windows support
• you want to avoid nightly/unstable Rust features

Facets

library · maturity active

concurrency http-server networking developer-tools backend performance microservices rust async-runtime io-uring thread-per-core epoll kqueue linux macos

Member repositories

For agents

markdown · JSON · MCP: product_card(name="monoio-rs/monoio")