#futures #tokio

tokio-threadpool

A task scheduler backed by a work-stealing thread pool.

7 releases

0.1.5 Jul 5, 2018
0.1.4 Jun 7, 2018
0.1.3 May 2, 2018
0.1.2 Mar 30, 2018
0.0.0 Feb 7, 2018

#6 in Concurrency

Download history 12964/week @ 2018-05-06 16757/week @ 2018-05-13 17264/week @ 2018-05-20 17152/week @ 2018-05-27 16150/week @ 2018-06-03 19573/week @ 2018-06-10 18987/week @ 2018-06-17 19159/week @ 2018-06-24 17596/week @ 2018-07-01 17528/week @ 2018-07-08 21294/week @ 2018-07-15 19804/week @ 2018-07-22 16283/week @ 2018-07-29

76,008 downloads per month

Tokio Thread Pool

A library for scheduling execution of futures concurrently across a pool of threads.

Why not Rayon?

Rayon is designed to handle parallelizing single computations by breaking them into smaller chunks. The scheduling for each individual chunk doesn't matter as long as the root computation completes in a timely fashion. In other words, Rayon does not provide any guarantees of fairness with regards to how each task gets scheduled.

On the other hand, tokio-threadpool is a general purpose scheduler and attempts to schedule each task fairly. This is the ideal behavior when scheduling a set of unrelated tasks.

Why not futures-cpupool?

It's 10x slower.

Examples

extern crate tokio_threadpool;
extern crate futures;

use tokio_threadpool::*;
use futures::*;
use futures::sync::oneshot;

pub fn main() {
    let (tx, _pool) = ThreadPool::new();

    let res = oneshot::spawn(future::lazy(|| {
        println!("Running on the pool");
        Ok::<_, ()>("complete")
    }), &tx);

    println!("Result: {:?}", res.wait());
}

License

This project is licensed under the MIT license.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in Tokio by you, shall be licensed as MIT, without any additional terms or conditions.

MIT license

Dependencies

Reverse deps