-
Notifications
You must be signed in to change notification settings - Fork 3k
Lars Holmberg edited this page Jul 31, 2020
·
43 revisions
Add things that you ran into and solved here! Anyone with a GitHub account can contribute!
If you have questions about Locust that are not answered here, please check StackOverflow, or post your question there. This wiki is not for asking questions but for answering them :)
How do I...
Increase my request rate/RPS
- Increase the number of users. In order to fully utilize your target system you may need a lot of simultaneous users.
- If response times are unexpectedly high and/or increasing as the number of users go up, then you have probably saturated the system you are testing and need to dig into why. This is not really a Locust problem, but here are some things you may want to check:
- resource utilization (e.g. CPU, memory)
- configuration (e.g. max threads for your web server)
- back end response times (e.g. DB)
- If Locust is complaining about high CPU usage on its side
- Run Locust distributed to utilize multiple cores & multiple machines
- Try switching to FastHttpUser to reduce CPU usage
Clear cookies, to make the next task iteration seem like a new user to my system under test
Call
self.client.cookies.clear()
at the end of your task.
Create a Locust file based on a recorded browser session
Try using Transformer
Check the list of issues (a lot of questions/misunderstandings are filed as issues)