You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have the following question:
looking at the example test you are running, looks like it is using a ramping-vus executor.
The project splits number of VUs based on the parallelizm value. E.g. paralellizm=4 => 50 VUs per pod
But does it has a built it logic for handling executors of constant-arrival-rate and zramping-arrival-rate` type? Will it split target rates too?
Thanks in advance for the answer and for this wonderful project you created!
The text was updated successfully, but these errors were encountered:
Hi @ostrovanka 👋 Yes, the logic is the same for any executor of k6. k6 Operator is not implementing any distribution on its own, it just utilizes methods already existing in k6, specifically execution segment options. The splitting is equal between all runners. I believe a similar question was brought up here before: #120
Hello, team!
I have the following question:
looking at the example test you are running, looks like it is using a
ramping-vus
executor.The project splits number of VUs based on the parallelizm value. E.g. paralellizm=4 => 50 VUs per pod
But does it has a built it logic for handling executors of
constant-arrival-rate
and zramping-arrival-rate` type? Will it split target rates too?Thanks in advance for the answer and for this wonderful project you created!
The text was updated successfully, but these errors were encountered: