Function conditional_append_under_contention
pub async fn conditional_append_under_contention<F: Fixture>(
open: impl AsyncFn() -> F,
params: BenchmarkParams,
) -> BenchmarkRecordAvailable on crate feature
bench only.Expand description
(b) Conditional append under k contenders, reporting the split.
One boundary event is seeded, then k handles each attempt a conditional append against the same boundary. Every one of the k is accounted for as committed, rejected, refused or failed, which is what makes a run where nobody collided legible as such rather than averaged away — ADR-0012 asked this instrument for a rejection mix, and a rejection count of zero is a measurement of the wrong thing however fast it was.
The k futures are built before any is polled and then driven
round-robin on one thread, so this imposes no Send bound. An adapter
that wants OS-thread contention supplies it from its own emitter.