Change optional Sleep to Rate in req/sec #24

New issue

Open

opened 2023-03-08 23:37:54 +00:00 by snegurochka · 6 comments

snegurochka commented

2023-03-08 23:37:54 +00:00

Member

Original issue: https://github.com/nspcc-dev/xk6-neofs/issues/15

Change optional Sleep to Rate in req/sec

Original issue: https://github.com/nspcc-dev/xk6-neofs/issues/15 - Change optional Sleep to Rate in req/sec

alexvanin commented

2023-03-10 09:16:37 +00:00

Owner

We can reuse some xk6 code to manage sleep time in yaml script, see https://k6.io/docs/using-k6/k6-options/reference/#minimum-iteration-duration
@a.bogatyrev please add some details.

We can reuse some xk6 code to manage sleep time in yaml script, see https://k6.io/docs/using-k6/k6-options/reference/#minimum-iteration-duration @a.bogatyrev please add some details.

alexvanin added the

label 2023-03-10 09:16:54 +00:00

fyrchik commented

2023-03-13 11:21:12 +00:00

Owner

Actually, I would expect this to already work with -e K6_MIN_ITERATION_DURATION=0.4s (or 40ms), for example.
Could you verify if this is true? @a.bogatyrev

Actually, I would expect this to already work with `-e K6_MIN_ITERATION_DURATION=0.4s` (or 40ms), for example. Could you verify if this is true? @a.bogatyrev

fyrchik commented

2023-03-13 11:35:55 +00:00

Owner

Note, that it is not the same as our SLEEP, it should include operation duration itself too.

mmalygina commented

2023-03-13 13:54:38 +00:00

Member

--min-iteration-duration works as expected, iteration duration is extended to match with provided value

/home/service/k6 run --min-iteration-duration 500ms   -e WRITERS=10  \
-e DURATION=10 -e WRITE_OBJ_SIZE=10 -e READERS=0 \
-e DELETERS=0 -e S3_ENDPOINTS=$S3ENDPOINTS \
-e PREGEN_JSON=/home/service/s3_4kb.json /home/service/scenarios/s3.js

running (10.0s), 00/10 VUs, 200 complete and 0 interrupted iterations
write ✓ [ 100% ] 10 VUs  10s
     █ setup

     █ teardown

     aws_obj_put_duration...: avg=67.43ms min=52.78ms med=67.13ms max=93.82ms p(90)=75.41ms p(95)=77.45ms
     aws_obj_put_total......: 200    19.95651/s
     data_received..........: 0 B    0 B/s
     data_sent..............: 2.0 MB 204 kB/s
     iteration_duration.....: avg=67.23ms min=7.69µs  med=67.52ms max=94.42ms p(90)=76.02ms p(95)=77.95ms
     iterations.............: 200    19.95651/s
     vus....................: 10     min=10     max=10
     vus_max................: 10     min=10     max=10

```--min-iteration-duration``` works as expected, iteration duration is extended to match with provided value ``` /home/service/k6 run --min-iteration-duration 500ms -e WRITERS=10 \ -e DURATION=10 -e WRITE_OBJ_SIZE=10 -e READERS=0 \ -e DELETERS=0 -e S3_ENDPOINTS=$S3ENDPOINTS \ -e PREGEN_JSON=/home/service/s3_4kb.json /home/service/scenarios/s3.js running (10.0s), 00/10 VUs, 200 complete and 0 interrupted iterations write ✓ [ 100% ] 10 VUs 10s █ setup █ teardown aws_obj_put_duration...: avg=67.43ms min=52.78ms med=67.13ms max=93.82ms p(90)=75.41ms p(95)=77.45ms aws_obj_put_total......: 200 19.95651/s data_received..........: 0 B 0 B/s data_sent..............: 2.0 MB 204 kB/s iteration_duration.....: avg=67.23ms min=7.69µs med=67.52ms max=94.42ms p(90)=76.02ms p(95)=77.95ms iterations.............: 200 19.95651/s vus....................: 10 min=10 max=10 vus_max................: 10 min=10 max=10 ```

🎉 1

fyrchik commented

2023-03-14 07:06:29 +00:00

Owner

Let's remove SLEEP* env variable from the code and documentation then.

Let's remove `SLEEP*` env variable from the code and documentation then.

fyrchik commented

2024-01-19 13:50:56 +00:00

Owner

--min-iteration-duration doesn't allow us to have different durations for mixed scenarios.
The distinction was introduced in ea604ee8ee -- @a.bogatyrev is it something we still use?

`--min-iteration-duration` doesn't allow us to have different durations for mixed scenarios. The distinction was introduced in ea604ee8ee36dacea5b5362b1 -- @a.bogatyrev is it something we still use?