Christopher Hunt e106c4d32b

benches: benchmark for things in block_on (#5440) ...

This additional benchmark exercises a common request/reply pattern using an MPSC for requests along with a oneshot payload as a reply mechanism. When used in a current threaded scenario, the bench is 17 times faster on my machine than when using the multi-threaded runtime and one worker thread. Not only that, but if I increase the number of worker threads to 6, performance degrades further.

Does this suggest a scheduling problem with the multi-threaded runtime?

No matter what, hopefully the benchmarks are a useful addition.

2023-02-14 23:05:10 +00:00

..

Cargo.toml

benches: benchmark for things in block_on (#5440)

2023-02-14 23:05:10 +00:00

copy.rs

io: make copy continue filling the buffer when writer stalls (#5066)

2022-10-03 12:58:21 +02:00

fs.rs

chore: fix newly added warnings (#4253)

2021-11-22 18:40:57 +09:00

rt_multi_threaded.rs

chore: fix typos (#3907)

2021-07-01 02:06:56 +09:00

signal.rs

rt: worker_threads must be non-zero (#2947)

2020-10-12 15:15:40 -04:00

spawn.rs

bench: update spawn benchmarks (#3927)

2021-07-07 10:52:53 +02:00

sync_mpsc_oneshot.rs

benches: benchmark for things in block_on (#5440)

2023-02-14 23:05:10 +00:00

sync_mpsc.rs

Move stream items into tokio-stream (#3277)

2020-12-15 20:24:38 -08:00

sync_rwlock.rs

sync: add #[must_use] to lock guards (#4886)

2022-08-09 13:44:29 +02:00

sync_semaphore.rs

rt: worker_threads must be non-zero (#2947)

2020-10-12 15:15:40 -04:00