Locust docker version 1.4.0 using 100% CPU on idle
See original GitHub issueTest environment: Ubuntu 18.04.1 Docker version 19.03.6
Environment stays the same only the docker image version is changed. Running the docker container with the same locustifle.py which is an example from https://hub.docker.com/r/locustio/locust
from locust import HttpUser, task
class QuickstartUser(HttpUser):
def on_start(self):
self.client.post
("/login", json={"username":"foo", "password":"bar"})
@task
def hello_world(self):
self.client.get("/hello")
self.client.get("/world")
@task(3)
def view_item(self):
for item_id in range(10):
self.client.get(f"/item?id={item_id}", name="/item")
When running locustio/locust version 1.3.2 the idle CPU load is around 0.0% and stable.
Running locustio/locust version 1.4.0 the idle CPU load goes up to 100.0% at once when the container is started and stays between 96.7% and 100.0%.
Issue Analytics
- State:
- Created 3 years ago
- Comments:17 (6 by maintainers)
Top Results From Across the Web
Idle docker using 100% cpu
When idle cpu usage should remain low. Actual behavior. Occasionally when idle I notice that see my cpu go to 100% (I notice...
Read more >Changelog Highlights — Locust 1.4.2 documentation
Fix 100% cpu usage when running in docker/non-tty terminal ... 0.13.4¶. Identical to previous version, but now built & deployed to Pypi using...
Read more >Docker Python Interpreter Extremely High CPU at Idle
After moving to the 2020.2 EAP any project I use a Docker python interpreter keeps 300+% CPU usage at all times. If I...
Read more >Setting the right requests and limits in Kubernetes - Learnk8s
How can you check the actual CPU and memory usage with the metrics server? Since the busybox container is idle, let's artificially generate...
Read more >Run A Custom Code With Locust Performance Testing ...
Generating a custom load shape Extending Locust using event hooks. ... Locust docker version 1.4.0 using 100% CPU on idle #1629. Merged pull...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Aha, the problem is that when running docker, there is no interactive terminal. Add
-it
to your docker run command as a temp workaround.I can reproduce this in docker/Ubuntu and it also prints the following exception when shutting down. I’m 99% confident this is an issue with keyboard input (on Ubuntu, not MacOS, CentOS or Windows), not with wait times.
I will check with @DennisKrone if he can fix it.