I ran the following script file to understand ramping arrival rate executor.
Command was k6 run fix-rpm-testing.js
export const options = {
scenarios: {
testing:{
executor: 'ramping-arrival-rate',
startRate: 100,
timeUnit: '1m',
preAllocatedVUs: 1,
maxVUs: 2,
stages: [
{ target: 100, duration: '1m' }
]
}
}
};
export default function (data) {}
And here is my console output
/\ |‾‾| /‾‾/ /‾‾/
/\ / \ | |/ / / /
/ \/ \ | ( / ‾‾\
/ \ | |\ \ | (‾) |
/ __________ \ |__| \__\ \_____/ .io
execution: local
script: fix-rpm-testing.js
output: -
scenarios: (100.00%) 1 scenario, 2 max VUs, 1m30s max duration (incl. graceful stop):
* testing: Up to 1.67 iterations/s for 1m0s over 1 stages (maxVUs: 1-2, gracefulStop: 30s)
running (1m00.0s), 0/1 VUs, 99 complete and 0 interrupted iterations
testing ✓ [======================================] 0/1 VUs 1m0s 2 iters/s
data_received........: 0 B 0 B/s
data_sent............: 0 B 0 B/s
iteration_duration...: avg=10.85µs min=5.17µs med=10.52µs max=49.92µs p(90)=12.37µs p(95)=27.14µs
iterations...........: 99 1.649874/s
vus..................: 1 min=1 max=1
vus_max..............: 1 min=1 max=1
What is the reason for 99 iterations instead of targeted value 100 even though I specified maxVUs:2
and it shows vus_max=1
?
Does that mean K6 never created 2nd VU even though it was unable to reach the target of 100 iteration ?