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. - Source: dev.to / about 2 months ago
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. - Source: dev.to / 10 months ago
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. Source: about 1 year ago
Gatling , this is what we tested concurrency with. Setting up might take a while depending on your exp. But the tool is solid. Source: about 1 year ago
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. - Source: dev.to / over 1 year ago
Load test your code to simulate a production load (you can use tools like k6 or Gatling). - Source: dev.to / over 1 year ago
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. Source: over 1 year ago
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. - Source: dev.to / over 1 year ago
JMeter is old and crusty and not at all friendly to work with. But I used it for years because it was really about the best we had. Today I don't wish it on anyone. Ruby JMeter finally made JMeter easier to manage, but I haven't worked in a Ruby shop for years, and I'm not going to force everyone to learn Ruby just to do some load testing. https://github.com/flood-io/ruby-jmeter Then along came k6. It's... - Source: Hacker News / over 1 year ago
I am running my gatling (https://gatling.io/) based load tests from inside a docker container . Last line in Dockerfile is. Source: over 1 year ago
I used to use JMeter, till someone else on the team introduced me to locust, so check that out if you don’t mind doing some python: https://locust.io. There’s also gatling (scala based, but can be generated by a recorder or HAR files), https://gatling.io. Source: over 1 year ago
I use nodemark to benchmark pure logic, not database interactions. If I wanted to benchmark the full application logic including database interactions, and I couldn't do it live, then I'd run my full app locally and smash it with ab, gatling or similar. Source: almost 2 years ago
Gatling or other tools like those mentioned here: https://www.reddit.com/r/devops/comments/llv5s7/best_way_to_benchmark_and_load_test_an_api/. Source: almost 2 years ago
As we are using Karate DSL for API testing, a straightforward choice would be to go with Gatling, as it nicely integrates with Karate DSL, and we can reuse our existing tests for performance testing. - Source: dev.to / about 2 years ago
I would look into https://gatling.io/. Source: over 2 years ago
What about https://gatling.io/? Been using it for close to a decade. Source: over 2 years ago
Another edit: If you actually don't care about the browser / website itself but more about the server, there are frameworks such as Gatling (https://gatling.io/) that allow you to execute many HTTP requests at (more or less) the same time. Source: almost 3 years ago
Before the initial release of an API, we benchmark our different endpoints (with the help of specialized tools like Locust, Gatling or k6) in order to:. - Source: dev.to / about 3 years ago
We are using https://gatling.io/ and can recommend. It's good also for more complex scenarios with websockets etc, and has better pricing than k6 when you need to get serious (500k+ virtual users, long scenarios..). Source: about 3 years ago
Do you know an article comparing gatling.io to other products?
Suggest a link to a post with product alternatives.
This is an informative page about gatling.io. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.