-
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
arrival-rate
executors do not report active VUs accurately, they report initialized VUs instead
#1977
Comments
Thanks for reporting this! We've known about for a while, but we lost sight of it... 😞 It is something halfway between a bug and a missing feature, one of the compromises for the sake of expedience to finally get #1007 out of the door last year... 😅 Its time to get fixed might have finally come, however, so I'll edit this issue a bit and keep it open. We probably should take care of it together with the rest of the items in #1386 and #1944 To give some details about the issue: currently, arrival-rate executors can easily show in the progress bars precisely how many active VUs they are using. However, since multiple scenarios can be executed simultaneously, and the |
arrival-rate
executors do not report active VUs accurately, they report initialized VUs instead
Thank you for the quick response |
Hello! |
Sorry @jsolv, nobody has worked on this yet. I added it to the next milestone, but I can't make any promises when we'll get to it... 😞 If someone wants to make a PR before we can, we can review it though! |
This is a somewhat quick and dirty fix of #1977, where instead of changing the global active VUs when the VU is activated, we change it when the VU is actually running. This synchronizes it with the running count of the internal activeVUPool, and reports the correct value everywhere the ExecutionState is used (the real-time total active VU count while the test is running, in all outputs, etc.).
This is a somewhat quick and dirty fix of #1977, where instead of changing the global active VUs when the VU is activated, we change it when the VU is actually running. This synchronizes it with the running count of the internal activeVUPool, and reports the correct value everywhere the ExecutionState is used (the real-time total active VU count while the test is running, in all outputs, etc.).
* Fix active VU reporting by arrival-rate executors This is a somewhat quick and dirty fix of #1977, where instead of changing the global active VUs when the VU is activated, we change it when the VU is actually running. This synchronizes it with the running count of the internal activeVUPool, and reports the correct value everywhere the ExecutionState is used (the real-time total active VU count while the test is running, in all outputs, etc.). * fixup! Fix active VU reporting by arrival-rate executors * fixup! Fix active VU reporting by arrival-rate executors * fixup! Fix active VU reporting by arrival-rate executors
In the console output of K6 you can easily see how many VUs are currently active. See picture k6 console output
In the .json output there is a metric "vus" and a metric "vus_max". I would expect "vus" to reflect the number of currently active virtual users. However, in my .json output, except for the entries where "vus" is 0, "vus" and "vus_max" always have the same value. See picture k6 .json output
Is this a bug? If not, how to generate the correct number of active VUs in the .json output?
The text was updated successfully, but these errors were encountered: