locust VS awesome-http-benchmark

I'm assuming this breaks a ton more than just my project (https://github.com/locustio/locust/actions/runs/4687344723/jobs/8315803536)

If, like me, AGPL isn't your cup of tea, you can look at vegeta or locust which are both MIT.

locust if you can code

Agreed with a lot of the points here, like starting small with a single piece of your API, then slowly expanding your tests once you’re comfortable that you know what you’re doing.

Note that if you use the Locust framework to write your load tests in Python, it takes care of measuring and reporting the latency and throughput for you. It’s really nice.

https://locust.io/

For my application, to tune these parameters I used a load testing tool. I built a script using Locust.

I have not used it myself but colleagues of mine recommend k6: https://k6.io/open-source/

There is also a Github repository keeping track of all the load-testing tools out there: https://github.com/denji/awesome-http-benchmark You will probably find something that will fit your bill.

I do not understand though why it is of any relevance what language the application is written in. Yes, it indicates a certain speed and novelty but you can write fast applications with good UX in other programming languages too.