Struct Schedule 

pub struct Schedule {
    pub pace: Option<Pace>,
    pub concurrency: usize,
}

When the steps run relative to one another.

The two fields are mutually exclusive in practice and the constructors say so, because they exist for opposite reasons. Pace spreads a run out to make it hard to recognise; overlapping compresses it into the smallest burst the endpoint will tolerate. A caller who asked for both would be asking to be unobtrusive quickly.

Fields

pace: Option<Pace>

concurrency: usize

Steps that may be in flight at once. 0 and 1 both mean sequential.

This is a step count, and steps are uneven — the capability battery is a dozen requests and stop_sequence is one — so it does not bound how much traffic reaches the endpoint. That bound is Client::with_limit, and a caller probing an endpoint it does not own wants both.

Implementations

impl Schedule

pub fn sequential() -> Self

One step at a time, in registry order. What every release before 0.5.0 did, and still the default.

pub fn paced(pace: Option<Pace>) -> Self

pub fn concurrent(n: usize) -> Self

Overlap up to n steps. Ignored while a Pace is set.

Trait Implementations

impl Clone for Schedule

fn clone(&self) -> Schedule

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Copy for Schedule

impl Debug for Schedule

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for Schedule

fn default() -> Schedule

Returns the “default value” for a type.