https://github.com/compio-rs/compio

A thread-per-core Rust runtime with IOCP/io_uring/polling.
https://github.com/compio-rs/compio

Last synced: about 1 month ago
JSON representation

A thread-per-core Rust runtime with IOCP/io_uring/polling.

• Host: GitHub
• URL: https://github.com/compio-rs/compio
• Owner: compio-rs
• License: mit
• Created: 2023-08-28T16:19:59.000Z (over 1 year ago)
• Default Branch: master
• Last Pushed: 2024-05-21T18:32:20.000Z (7 months ago)
• Last Synced: 2024-05-22T11:30:21.300Z (7 months ago)
• Language: Rust
• Homepage:
• Size: 1.39 MB
• Stars: 287
• Watchers: 2
• Forks: 25
• Open Issues: 7
• Metadata Files:
  • Readme: README.md
  • Contributing: CONTRIBUTING.md
  • License: LICENSE
  • Code of conduct: CODE_OF_CONDUCT.md

Awesome Lists containing this project

• awesome-iouring - compio

README

        
# Compio

[![MIT licensed](https://img.shields.io/badge/license-MIT-blue.svg)](https://github.com/compio-rs/compio/blob/master/LICENSE)

[![crates.io](https://img.shields.io/crates/v/compio)](https://crates.io/crates/compio)

[![docs.rs](https://img.shields.io/badge/docs.rs-compio-latest)](https://docs.rs/compio)

[![Check](https://github.com/compio-rs/compio/actions/workflows/ci_check.yml/badge.svg)](https://github.com/compio-rs/compio/actions/workflows/ci_check.yml)

[![Test](https://github.com/compio-rs/compio/actions/workflows/ci_test.yml/badge.svg)](https://github.com/compio-rs/compio/actions/workflows/ci_test.yml)

[![Telegram](https://img.shields.io/badge/Telegram-compio--rs-blue?logo=telegram)](https://t.me/compio_rs)

A thread-per-core Rust runtime with IOCP/io_uring/polling.

The name comes from "completion-based IO".

This crate is inspired by [monoio](https://github.com/bytedance/monoio/).

## Why not Tokio?

Tokio is a great generic-purpose async runtime.

However, it is poll-based, and even uses [undocumented APIs](https://notgull.net/device-afd/) 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 expose 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.12.0", features = ["macros"] }

```

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

```rust

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

#[compio::main]

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.

## Contributing

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](https://t.me/compio_rs). Before contributing, please checkout our [contributing guide](https://github.com/compio-rs/compio/blob/master/CONTRIBUTING.md).