Skip to content

Latest commit

 

History

History

steps

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 

Load Steps

1. Identification

The load step ids are used primarily to distinguish the load step results.

java -jar mongoose-<VERSION>.jar --load-step-id=custom_test_0 ...

See also the output reference

2. Type

2.1. Linear

Linear load step type is used by default and may be considered as a straightforward way to generate a load.

2.2. Weighted

Weighted load step type is additional and requires the WeightedLoad extention. Weighted load extension, allowing to generate 20% write and 80% read operations, for example.

2.3. Pipeline

Pipeline load step type is additional and requires the PipelineLoad extention. Load operations pipeline (create, delay, read-then-update, for example), extension.

3. Limits

By default the load steps are not limited explicitly. There are several ways to limit the load steps execution.

3.1. Operations Count

Limit the load step by the operation count:

java -jar mongoose-<VERSION>.jar --load-op-limit-count=1000000 ...

3.2. Time

Limit the load step by the time (5 minutes):

java -jar mongoose-<VERSION>.jar --load-step-limit-time=5m ...

3.3. Transfer Size

Limit the load step by the transfer size:

java -jar mongoose-<VERSION>.jar --load-step-limit-size=1.234TB ...

3.4. End Of Input

"EOI" = "End Of Input"

A load step is also limited by the load operations EOI. End of the load operations input is reached if:

  • Load operations recycling is disabled and end of the items EOI is reached
  • Load operations recycling is enabled but all the load operations are failed (there's no successfull load operations to recycle)