You can practice what you learned over there: https://15puzzle.netlify.app/. Source: almost 2 years ago

I spent 2 days practicing this and now get times in the 30 - 60 second range. I'm not a genius. So it's just not as hard as it seems. Try yourself: https://15puzzle.netlify.app/. Source: about 3 years ago

Our test duration was 2 days. To handle this longer testing period, we switched from BlazeMeter (max test duration of 20 minutes) to Locust, an open-source load-testing tool. - Source: dev.to / 5 days ago

This week at work I was tasked with continuing some load testing that a previous Engineer had started. They had used locust which is an open source load testing tool to run the initial load testing on the staging environment. I now needed to do the same for production so I followed in their footsteps. - Source: dev.to / about 1 month ago

Finally, let's compare the response time of the requests. For that, we will use Locust , an open source load testing tool. The tests will run for 5 minutes, and will increase 4 requests per second every second until they reach 1000 requests per second. - Source: dev.to / 4 months ago

Locust: Another open-source tool, Locust is particularly flexible due to its support for Python scripts. It can conduct load tests across multiple machines, making it possible to simulate millions of users simultaneously. An exceptional feature of Locust is its web-based UI, which allows real-time tracking of performance metrics during test execution. - Source: dev.to / 4 months ago

Locust is a perfect tool to use on such occasion:. - Source: dev.to / 4 months ago