Scenarios `grpc.js`, `http.js` and `s3.js` support the following options:
*`DURATION` - duration of scenario in seconds.
*`READERS` - number of VUs performing read operations.
*`WRITERS` - number of VUs performing write operations.
*`REGISTRY_FILE` - if set, all produced objects will be stored in database for subsequent verification. Database file name will be set to the value of `REGISTRY_FILE`.
*`WRITE_OBJ_SIZE` - object size in kb for write(PUT) operations.
*`PREGEN_JSON` - path to json file with pre-generated containers and objects (in case of http scenario we use json pre-generated for grpc scenario).
*`SLEEP` - time interval (in seconds) between VU iterations.
Examples of how to use these options are provided below for each scenario.
*`GRPC_ENDPOINTS` - GRPC endpoints of neoFS in format `host:port`. To specify multiple endpoints separate them by comma.
*`DELETERS` - number of VUs performing delete operations (using deleters requires that options `DELETE_AGE` and `REGISTRY_FILE` are specified as well).
*`DELETE_AGE` - age of object in seconds before which it can not be deleted. This parameter can be used to control how many objects we have in the system under load.
## HTTP
1. Create pre-generated containers or objects:
There is no dedicated script to preset HTTP scenario, so we use the same script as for gRPC:
*`S3_ENDPOINTS` - endpoints of S3 gateways in format `host:port`. To specify multiple endpoints separate them by comma.
*`DELETERS` - number of VUs performing delete operations (using deleters requires that options `DELETE_AGE` and `REGISTRY_FILE` are specified as well).
*`DELETE_AGE` - age of object in seconds before which it can not be deleted. This parameter can be used to control how many objects we have in the system under load.
*`OBJ_NAME` - if specified, this name will be used for all write operations instead of random generation.
This scenario allows to verify that objects created by a previous run are really stored in the system and their data is not corrupted. Running this scenario assumes that you've already run gRPC or HTTP or S3 scenario with option `REGISTRY_FILE`.
Scenario picks up all objects in `created` status. If object is stored correctly, its' status will be changed into `verified`. If object does not exist or its' data is corrupted, then the status will be changed into `invalid`.
*`CLIENTS` - number of VUs for verifying objects (VU can handle both GRPC and S3 objects)
*`TIME_LIMIT` - amount of time in seconds that is sufficient to verify all objects. If this time interval ends, then verification process will be interrupted and objects that have not been checked will stay in the `created` state.
*`REGISTRY_FILE` - database file from which objects for verification should be read.
*`SLEEP` - time interval (in seconds) between VU iterations.