FAQ

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...

Sort out installation issues

See Installation

Increase my request rate/RPS

1. Increase the number of users. In order to fully utilize your target system you may need a lot of simultaneous users.
2. 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 & network. Check these metrics on the locust side as well)
• configuration (e.g. max threads for your web server)
• back end response times (e.g. DB)
• client side DNS performance/flood protection (Locust will normally make at least one DNS Request per User)

3. If Locust is complaining about high CPU usage on its side (WARNING/root: CPU usage above 90%! ...)

• Run Locust distributed to utilize multiple cores & multiple machines
• Try switching to FastHttpUser to reduce CPU usage

4. If you are using a custom client (not HttpUser or FastHttpUser), make sure any client library you are using is gevent-friendly, otherwise it will block the entire Python process (essentially limiting you to one user per worker)

Resolve errors that occur during load (error 5xx, Connection aborted, Connection reset by peer, etc)

Check your server logs. If it works at low load then it is almost certainly not a Locust issue, but an issue with the system you are testing.

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.

Control headers or other things about my HTTP requests

Locust's client in HttpUser inherits from requests and the vast majority of parameters and methods for requests should just work with Locust. Check out the docs and Stack Overflow answers for requests first and then ask on Stack Overflow for additional Locust specific help if necessary.

Create a Locust file based on a recorded browser session

Try using Transformer

How to run a Docker container of Locust in Windows Subsystem for Linux (Windows 10 users)?

If you use WSL on a Windows computer, then you need one extra step than the "docker run ..." command: copy your locusttest1.py to a folder in a Windows path on your WSL and mount that folder instead of your normal WSL folder:

$ mkdir /c/Users/[YOUR_Windows_USER]/Documents/Locust/
$ cp ~/path/to/locusttest1.py /c/Users/[YOUR_Windows_USER]/Documents/Locust/
$ docker run -p 8089:8089 -v /c/Users/[YOUR_Windows_USER]/Documents/Locust/:/mnt/locust locustio/locust:1.3.1 -f /mnt/locust/locusttest1.py

How to run locust on custom endpoint

Prefix the the endpoint to all @app.route definitions in locust/web.py file & also change as follows (where /locust is new endpoint)

app = Flask(__name__, static_url_path='/locust')

Change the entries of static content location in file locust/templates/index.html.

Eg: <link rel="shortcut icon" href="{{ url_for('static', filename='img/favicon.ico') }}" type="image/x-icon"/>

Check the list of issues (a lot of questions/misunderstandings are filed as issues)