Fibre Oneshot benchmarks

Throughput in Melem/s: Million items per second per item sent, median of samples. The best result in each row is highlighted. In batched tables, the bracketed figure is the gain over the same implementation's single-item row. A dash means the implementation has no channel for that cell. Measured on MacBook M4 Pro (14 cores).

Two stages, because a oneshot's channel is consumed by the op rather than standing across the run. full-cycle creates, sends and receives on one thread, so construction is part of the op and allocation shows. handoff pre-creates every pair before the barrier and times a sending thread against a receiving one, which is the same accounting the other pages use.

fibre appears four times: fibre is the clonable oneshot(), fibre-exclusive the single-sender exclusive(), and fibre-pool and fibre-pool-host take their slots from a standing pool instead of allocating. kanal, flume, crossbeam, async-channel and std have no oneshot and are absent rather than approximated with a bounded(1), which is a standing channel that happens to hold one item. futures and async-oneshot have no blocking receive and sync-oneshot has no Future, so each of those runs one mode only.

Handoff rows carry a lower item ceiling than the rest of the arena, since every op needs its own pre-created channel and the item count is also the resident channel count.