-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Segmentation issues #1514
Comments
import http from 'k6/http';
import { sleep } from 'k6';
export let options = {
vus: 0,
executionSegment: "1/3:2/3",
executionSegmentSequence: "0,1/3,2/3,1",
stages: [
{ target: 60, duration: "10s" },
{ target: 0, duration: "10s" },
],
}
export default function () {
http.get('https://test.k6.io');
sleep(1);
} you'd see something like this in the UI:
Notice how the times are formatted... My gut feeling is that the execution plan for this segment is correct, i.e. we don't have any work to do after |
This was an initial attempt to solve the first point from #1514, but there were a few blockers: - #1499 - #1427 - #1386 (comment)
Points 2 and 3 of this issue should have been fixed by #1535, but the first point might have to wait until #1499 / #1427 😭 The current lack of config+tuple abstraction is just making fixing this a huge error-prone PITA when it comes to the So, yeah, this should probably be left for v0.28.0, after we refactor the above issues. I've started some of the work ee17425, but I'll probably leave it at that, for now... 😞 |
Closing this, since 2/3 of the issues were fixed and remainder is mentioned in #1427 (comment) |
I'll use this issue to note some minor issues with the execution segmentation I've stumbled upon while testing #1007
will have a discrepancy between the description and actual execution:
Notice it say
33 looping VUs
in the description, but in reality we'll run 34 (as it says in 2 other places above) - we probably use the old scaling algorithm for the description and the striping algorithm for the actual implementation... If that's the case, we should probably fix #1499 / #1427 firstThe text was updated successfully, but these errors were encountered: