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

Better arrival-rate message when it can't hit rate #3664

Open
mstoykov opened this issue Mar 26, 2024 · 0 comments
Open

Better arrival-rate message when it can't hit rate #3664

mstoykov opened this issue Mar 26, 2024 · 0 comments

Comments

@mstoykov
Copy link
Collaborator

Feature Description

Currently if an arrival-rate scenario can't hit the provided rate there is a single warning message.

varr.logger.Warningf("Insufficient VUs, reached %d active VUs and cannot initialize more", maxVUs)

While this message is okay in general there are a lot of users who do not pay it much attention or do not understand that this means the SUT was not fast enough or preallocatedVUs/maxVUs was set too low.

Suggested Solution (optional)

For starters maybe rewrite the message to make it more clear that this very likely is a problem they should look into.

Maybe move it to an error instead of a warning - like this literally means the configured scenario could not do what it was supposed to do

Already existing or connected issues / PRs (optional)

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant