Can Criterion measure things after doing a per-iteration setup?

[faern]

Currently we have one benchmark to measure the time it takes to create a channel and another one to measure how long it takes to create a channel plus send a message on it. Because the channel is consumed by the send we need a new channel for each iteration. But does Criterion allow doing a per-iteration setup and then start timing? Something like:

b.iter(|| {
    let (sender, _receiver) = oneshot::channel();
    // Start measure time here!
    sender.send(black_box(value_fn())).unwrap()
});

If not, does it allow pairing one benchmark with another and say that the result of one should be subtracted from the other before presenting it? 🤷

[sandersaares]

You can use iter_custom which basically is "run some code for iters iterations and return the total Duration of those iters iterations". Alternatively, there is iter_batched which has unmeasured setup+teardown phases.

Oh, looking at the date this is ancient history, I wonder if even relevant for latest revision :)