locust load testing example

# This locust test script example will simulate a user # browsing the Locust documentation on https://docs.locust.io import random from locust import HttpUser, between, task from pyquery import PyQuery class AwesomeUser(HttpUser): host = "https://docs.locust.io/en/latest/" # we assume someone who is browsing the Locust docs, # generally has a quite long waiting time (between # 10 and 600 seconds), since there's a bunch of text # on each page wait_time = between(10, 600) def on_start(self): # start by waiting so that the simulated users # won't all arrive at the same time self.wait() # assume a

Blazemeter

blazemeter.com › blog › locust-load-testing

The Definitive Guide to Locust Load Testing | Perforce BlazeMeter

Step 05: Implement a method called on_start that will be executed at the start of our test file. The example described in this section can be found below: import time from locust import HttpUser, task, between class AuthenticateUser(HttpUser): timer = between(1, 10) @task def authenticate_task(self): self.client.get("/login") self.client.get("/register") def on_start(self): self.client.post("/register", json={"username":"testuser", "email":"test@test.com", "password":"password"})

Discussions

What sort of tools can I use to load test infrastructure that I’m building?

Without knowing more about your needs and any more specifics than the fact that your stack is fronted by a web endpoint, I recommend “bees with machine guns” because it has a silly fun name. https://github.com/newsapps/beeswithmachineguns That said, there are full-on APM platforms out there, several very tried and true like new relic and app dynamics (no affiliation with either) that will give you a picture of your whole stack under load. Sure, your app doesn’t fail until 10,000 hits in a minute or whatever. What failed at 10,001? Was it CPU at the web layer? Was it disk I/O at the database? Did your cache need tuning? Did your API layer fail to garbage collect and began swapping? These are questions 2 thru 6 after you answer question #1, which is “when does my app fail.” If you just load test, you can throw capacity (money) at the problem until you meet your needs... or start answering the “why” question and not just “when” about your stack’s limits, and when you meet them hard. More on reddit.com

r/devops

October 12, 2018

Load testing? A beginner guide on how to get started

Hi, best way is to check all metrics and search for anomalies. First metrics I check are: 90 and 99 percentiles latencies errors or other responses Resources on host (CPU, ram, disk) For more information you can check my collection https://github.com/mgasiorowski/performance_testing#web-links More on reddit.com

r/devops

October 20, 2020

Open Source Load Testing with Locust: 13 years, 60 million downloads later

Just wanted to say big thank you for working on this great tool I’ve been using Locust for some time now mainly for HA testing for our clustered application It is much more simpler than using Gatling! More on reddit.com

r/Python

192

January 24, 2025

How do I add auth headers to locust?

'Authorization:': should be 'Authorization': Also, this isn't locust specific. Iirc Locust uses Requests, so in the future I'd just tag it Requests and read their docs if you hit issues. May be wrong - Dig into the source code if you wanna confirm. More on reddit.com

r/learnpython

March 1, 2020

Videos