Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: How does this project split rate between pods? #209

Closed
ostrovanka opened this issue Mar 24, 2023 · 2 comments
Closed

Question: How does this project split rate between pods? #209

ostrovanka opened this issue Mar 24, 2023 · 2 comments
Labels
question Further information is requested

Comments

@ostrovanka
Copy link

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!

@yorugac
Copy link
Collaborator

yorugac commented Mar 27, 2023

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

Hope that answers the question!

@yorugac yorugac added the question Further information is requested label Mar 27, 2023
@yorugac
Copy link
Collaborator

yorugac commented May 3, 2023

Closing as this seems to be resolved. Please feel free to re-open if needs be.

@yorugac yorugac closed this as completed May 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants