Data items are used by default. The exact meaning may depend on the storage selected for the test. This is a file in case of the filesystem storage, object in case of Atmos/S3/Swift storage.
The item-data-size configuration option is used to specify the payload size for any new data items.
Fixed data item size is used by default. The default size value is 1MB.
java -jar mongoose-<VERSION>.jar --item-data-size=10KB ...It's possible to use the random size for the new items within the specified range:
java -jar mongoose-<VERSION>.jar --item-data-size=5MB-15MB ...The payload size for the new items may be also biased to the lower either upper bound:
java -jar mongoose-<VERSION>.jar --item-data-size=0-100MB,0.2 ...Note:
- The bias value is appended to the range after the comma (0.2 in the example above).
- The generated value is biased towards the high end if bias value is less than 1.
- The generated value is biased towards the low end if bias value is more than 1.
Note:
Same
item-data-input-*configuration options should be used forcreate,updateandreadload operations. The content verification read capability will not work correctly otherwise.
The uniform random data payload is used by default. It uses the configurable seed number to pre-generate some amount (4MB by default) of the random uniform data. To use the custom seed use the following option:
java -jar mongoose-<VERSION>.jar --item-data-input-seed=5eed42b1gb00b5 ...java -jar mongoose-<VERSION>.jar --item-data-input-file=<PATH_TO_CONTENT_FILE>The path items type may be useful to work with directories/buckets/containers (depending on the storage driver type used):
java -jar mongoose-<VERSION>.jar --item-type=path ...There are also an additional item type which may represent some storage-specific tokens like subtenant(Atmos) or auth token (Swift):
java -jar mongoose-<VERSION>.jar --item-type=token ...