[#121] scenarios: Fix tags doc
All checks were successful
DCO action / DCO (pull_request) Successful in 3m49s
Tests and linters / Tests (1.21) (pull_request) Successful in 6m18s
Tests and linters / Tests with -race (pull_request) Successful in 6m56s
Tests and linters / Tests (1.20) (pull_request) Successful in 2m53s
Tests and linters / Lint (pull_request) Successful in 2m25s

Signed-off-by: Dmitrii Stepanov <d.stepanov@yadro.com>
This commit is contained in:
Dmitrii Stepanov 2024-01-30 15:54:15 +03:00
parent 5cfb958a18
commit d1578a728f

View file

@ -20,7 +20,7 @@ Scenarios `grpc.js`, `local.js`, `http.js` and `s3.js` support the following opt
* `SELECTION_SIZE` - size of batch to select for deletion (default: 1000).
* `PAYLOAD_TYPE` - type of an object payload ("random" or "text", default: "random").
* `STREAMING` - if set, the payload is generated on the fly and is not read into memory fully.
* `METRIC_TAGS` - `instance` tag value.
* `METRIC_TAGS` - custom metrics tags (format `tag1:value1;tag2:value2`).
Additionally, the profiling extension can be enabled to generate CPU and memory profiles which can be inspected with `go tool pprof file.prof`:
```shell