locust VS Gatling

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.

Gatling: An open-source load and performance testing tool primarily designed for web applications, Gatling utilizes a simple domain-specific language (DSL) for creating and maintaining test scripts. It supports HTTP/2 and allows recording and generation of scenarios directly from a browser. The tool also provides detailed performance reports that are easy to analyze.

Performance and load testing are essential parts of GraphQL API testing. It ensures APIs can handle expected traffic volumes and respond within acceptable timeframes. You can use tools like Apache JMeter or Gatling to generate realistic loads and evaluate the API's performance under different scenarios. Techniques like batched queries and caching can help mitigate this issue.

New to the .NET community and trying to learn! I have used tools such as Apache JMeter (Java), gatling.io (Java) and Locust (Python) that are decent full featured web perf frameworks. Typically these integrate well with your code, and can be run as part of your unit/integration tests and produce offline reports

Gatling , this is what we tested concurrency with. Setting up might take a while depending on your exp. but the tool is solid.

I used SpringBoot 3.0.2, GraalVM 22 (JVM mode), a MacOS 2,6 GHz 6-Core Intel Core i7, running 1000 users for 5 minutes. The idea was to test how memory consumption and CPU usage evolve. Below, I compared the footprint of these three solutions. I collected the total count of requests, throughput, memory consumption, and CPU usage using VisualVM and Gatling.

Load test your code to simulate a production load (you can use tools like k6 or Gatling)

k6 is our preferred javascript based cloud tester for light webservices. gattling if you have (a monolith with) workflows and need more formalized code to prove/audit your testing.

It's read as "Ochikisu" and origin is the machine gun manufacturer Hotchkiss because this tool does not have as much firepower as the Gatling.