Gatling VS k6

Use load testing tools like Apache JMeter, Gatling, or Locust to measure your application's throughput under various loads and compare it to historical data.

Gatling: Known for its ease of use and support for high-concurrency simulations.

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.

K6 GitHub Repository

Repositório GitHub do K6

To perform stress testing on the eshop_gw API gateway service and verify the system's performance under high concurrency, use the stress testing tool k6. Before conducting the stress test, ensure that enough stock is set to avoid order failure.

Grafana K6 is another Grafana project that is looking for help. K6 is an open-source, distributed, and load testing tool that allows you to test the performance of your web applications in a scalable and realistic way.

I know this is about Desktop HTTP testing but has anyone experimented with command-line HTTP testing?

I recall having a good experience with https://github.com/grafana/k6 some eons ago.

It's geared towards writing load testing in JS but it also allows you to check HTTP body, headers, etc.

K6' usage - pretty friggin robust - is here https://github.com/grafana/k6/tree/master/js

k6 allows you to build performant load tests that take a fraction of the resources legacy load-testing tools require. The tests are written in an easy-to-follow JavaScript form and can be extended with a number of extensions. The tests execute via a Go-JavaScript compiler so they take a minimal amount of resources when being executed, allowing the scaling of load tests with fewer resources.

I’d use K6 for this. It’s been optimised for this purpose. https://github.com/grafana/k6