Struct trawler::WorkloadBuilder [] [src]

pub struct WorkloadBuilder<'a> { /* fields omitted */ }

Set the parameters for a new Lobsters-like workload.

Methods

impl<'a> WorkloadBuilder<'a>
[src]

[src]

Set the memory and request scale factor for the workload.

A factor of 1 generates a workload commensurate with what the real lobste.rs sees. At memory scale 1, the site starts out with ~40k stories with a total of ~300k comments spread across 9k users. At request factor 1, the generated load is on average 44 requests/minute, with a request distribution set according to the one observed on lobste.rs (see data/ for details).

[src]

Set the number of threads used to issue requests to the backend.

Each thread can issue in_flight requests simultaneously.

[src]

Set the runtime for the benchmark.

[src]

The maximum number of outstanding request any single issuer is allowed to have to the backend. Defaults to 20.

[src]

Instruct the load generator to store raw histogram data of request latencies into the given file upon completion.

If the given file exists at the start of the benchmark, the existing histograms will be amended, not replaced.

impl<'a> WorkloadBuilder<'a>
[src]

[src]

Run this workload with clients spawned from the given factory.

If prime is true, the database will be seeded with stories and comments according to the memory scaling factory before the benchmark starts. If the site has already been primed, there is no need to prime again unless the backend is emptied or the memory scale factor is changed. Note that priming does not delete the database, nor detect the current scale, so always empty the backend before calling run with prime set.

Trait Implementations

impl<'a> Default for WorkloadBuilder<'a>
[src]

[src]

Returns the "default value" for a type. Read more

Auto Trait Implementations

impl<'a> Send for WorkloadBuilder<'a>

impl<'a> Sync for WorkloadBuilder<'a>