-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Fail to spawn fixed users when run with DoubleWave load shape #2345
Comments
@EzR1d3r I think this is ”your” code? Could you have a look? |
Ok, I will when have enought time, may be at weekend. |
I have repeated the bug. I guess I know how to fix, but I have to check. |
@cyberw I am trying to run tests locally, but I have the error.
|
I dont remember that issue. That file should be generated when doing pip install (e.g. |
This is what mine looks like after installing:
|
Thx, it works for test_dispatch.py. It is enought for me, but with test_main.py it raises an import error with termios module (on win). I am not sure, but it will work only on linux, or I am wrong? |
On windows it is supposed to import win32console instead of termios. But never mind. Is the change ready for merge?
|
No, I still didn't add the test for this case. I will mention when it be ready. |
fixed in #2350 |
Describe the bug
When running DoubleWave load shape with both fix count user and spawn users, during spawning new users, locust will first check the fixed user count using blow codes(dispatch.py)
If
current_fixed_users_count[user_name] >= fixed_users[user_name].fixed_count:
, it will start loop with below warning:CPU usage above 90%! This may constrain your throughput and may even give inconsistent response time measurements!
Expected behavior
Locust should spawn DoubleWave load shape with fixed count users.
Actual behavior
Locust will get stuck when spawning new users if the current fixed user count is equal expected fixed user count.
Steps to reproduce
locust -f locustfile.py --host https://www.bing.com
Environment
The text was updated successfully, but these errors were encountered: