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.

Sign up for GitHub

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

Jump to bottom

Segment --rps option between instances #1341

Closed
na-- opened this issue Mar 2, 2020 · 2 comments
Closed

Segment --rps option between instances #1341

na-- opened this issue Mar 2, 2020 · 2 comments
Labels
cloud evaluation needed proposal needs to be validated or tested before fully implementing it in k6 executors lower prio

Comments

@na--
Copy link
Member

na-- commented Mar 2, 2020

When a test is executed between multiple instances, the rps option value probably should be partitioned between them.
@na-- na-- added lower prio evaluation needed proposal needs to be validated or tested before fully implementing it in k6 executors cloud labels Mar 2, 2020
@na--
Copy link
Member Author

na-- commented Apr 22, 2020

__VU as well (there was another mention of this, I think)

@na-- na-- added this to the v1.0.0 milestone Apr 22, 2020
@na-- na-- modified the milestones: v1.0.0, v0.28.0 May 21, 2020
@na-- na-- modified the milestones: v0.28.0, v0.29.0 Sep 9, 2020
@na-- na-- removed this from the v0.29.0 milestone Nov 3, 2020
@na--
Copy link
Member Author

na-- commented Dec 3, 2020

For backwards compatibility, we are probably not going to implement this issue at all, and leave the __VU and --rps behavior as it is. Instead of segmenting __VU (i.e. having the __VU constant be unique across multiple instances in a cloud run), we plan to add new helper methods for accessing such script execution information (#1320), including a globally unique VU number. And we're trying to discourage --rps usage now that we have arrival-rate executors, though we'd probably have some similar mechanism in the future HTTP API, which should probably be segmented by default.

@na-- na-- closed this as completed Dec 3, 2020
@na-- na-- mentioned this issue Jan 13, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cloud evaluation needed proposal needs to be validated or tested before fully implementing it in k6 executors lower prio
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@na--