12 releases (breaking)

0.9.0-beta.3 Nov 24, 2023
0.8.0 Oct 7, 2023

#675 in Asynchronous

Download history 9/week @ 2023-08-23 53/week @ 2023-08-30 49/week @ 2023-09-06 29/week @ 2023-09-13 33/week @ 2023-09-20 12/week @ 2023-09-27 21/week @ 2023-10-04 2/week @ 2023-10-11 32/week @ 2023-10-18 18/week @ 2023-10-25 4/week @ 2023-11-01 4/week @ 2023-11-08 187/week @ 2023-11-15 104/week @ 2023-11-22 104/week @ 2023-11-29

402 downloads per month
Used in 2 crates

MIT license

6.5K SLoC


MIT licensed crates.io docs.rs Azure DevOps builds

A thread-per-core Rust runtime with IOCP/io_uring/polling. The name comes from "completion-based IO". This crate is inspired by monoio.

Why not Tokio?

Tokio is a great generic-propose async runtime. However, it is poll-based, and even uses undocumented APIs on Windows. We would like some new high-level APIs to perform IOCP/io_uring.

Unlike tokio-uring, this runtime isn't Tokio-based. This is mainly because that no public APIs to control IOCP in mio, and tokio won't public APIs to control mio before mio reaches 1.0.

Why not monoio/tokio-uring/glommio?

They don't support Windows.

Quick start

Add compio as dependency:

compio = { version = "0.9.0-beta.1", features = ["macros"] }

Then we can use high level APIs to perform filesystem & net IO.

use compio::{fs::File, io::AsyncReadAtExt};

async fn main() {
    let file = File::open("Cargo.toml").await.unwrap();
    let (read, buffer) = file.read_to_end_at(Vec::with_capacity(1024), 0).await.unwrap();
    assert_eq!(read, buffer.len());
    let buffer = String::from_utf8(buffer).unwrap();
    println!("{}", buffer);

You can also control the low-level driver manually. See driver example of the repo.


There are opportunities to contribute to Compio at any level. It doesn't matter if you are just getting started with Rust or are the most weathered expert, we can use your help. If you have any question about Compio, feel free to join our telegram group. Before contributing, please checkout our contributing guide.


~97K SLoC