Gatling Reviews

If you are looking for a powerful and modern tool for performance testing, Gatling is one of the best options on the market. Its non-blocking architecture allows it to simulate thousands of users with efficient resource consumption, and its code-based approach facilitates integration with CI/CD pipelines. Additionally, it generates detailed, visual, and easy-to-interpret reports. Ideal for technical teams that need precision, speed, and automation in their load testing.

What I would like to see in Gatling is a more united and active community, where sharing best practices, use cases, and support among users is more common. Additionally, I believe that more concise and structured documentation would help a lot, especially for those who are starting or want to integrate Gatling quickly into their pipelines. Even so, it is a very powerful and efficient tool for performance testing.

Gatling solves the challenge of performing efficient, scalable, and maintainable performance testing. Its code-based approach allows me to automate load tests, easily integrate them into my CI/CD pipelines, and version them as part of the project. Thanks to its non-blocking architecture, I can simulate thousands of concurrent users without compromising system resources. This has allowed me to detect bottlenecks, validate the stability of my services, and deliver more robust and reliable software in less time.

One of the first tools I used for performance testing, and to this day, it's still the one I use the most to run large-scale tests. It's lightweight, captures flows easily with its recorder, and the logs are easy to understand—making Gatling, for me, the perfect tool for my analyses.

- Excellent (dynamic) reporting

I have used only Open Source version in few of my projects. I have used both Scala and Java versions. It's quite easy to set up, DSL is rreach.

Compared to GUI based tools here we have code - so one can apply all good coding practices and IDE support.

It can be easily integrated into your CI pipeline.

Java version compared to Scala lacked some small features when it comes to some advanced usage.

java/maven tool with posibilites integrating into current java projects (with a maven plugin help). Native integration with Github Actions. Gatling enteprise provides meaninful graphs & stats for A/B testing. Gatling Enterprise support is responsive and valuable.

No native integrations with monitoring tools (DataDog. etc).

No test scehduler.

Release-to-Release API perfromance tests for web-faced application.

It is so easy and intuitive to use. The graphs show all kinds of information.

Hm, not sure if I dislike something about Gatling. It just makes sense.

We need to determine how our API endpoint behaves under load from users.

As an open-source performance testing tool, it excels at its intended purpose, particularly by efficiently invoking virtual users without impacting your local computer's resources.

I invested a significant amount of time learning how to accomplish tasks with limited examples. Like any new tool, there was a learning curve involved. Initially, I focused on learning Gatling by studying the Scala DSL, which had a richer set of examples available. This helped me validate specific aspects against packaged software. Later, I transitioned to the Java DSL, which offered a smaller pool of examples for reference.

Gatling plays a crucial role in performance validation of page transitions. While application configurations often perform satisfactorily, integrating various components can lead to performance degradation. Gatling can effectively identify and address these areas of concern.

The ability to describe load tests in an expressive, readable DSL (Domain Specific Language) is wonderful. It helps with understanding and documentation of tests. The non-blocking request model used underneath results in a scalable load test framework.

More protocol support would be helpful to test legacy systems.

The ability to describe load tests in an expressive, readable DSL (Domain Specific Language) is a huge benefit. Load tests are able to be code reviewed and versioned controlled much like the rest of the software.

We needed to do performance testing on our mobile application then. It was Gatling that allowed us to achieve our goal and expose specific components that was causing bottlenecks. The flexibility of Scala allowed us to be creative in the performance development. The automatic capture of objects was also helpful and made it easier.

Nothing really. It worked well for us. Although our team was technical and learned to use Scala on the fly. It was fairly straightforward.

Exposing the specific calls to the backend especially when doing the load test.

- Gatling is easy to use (even when you do not know Scala at all! I wrote tests on my first day)

- Good OOTB reporting

- Gatling Scala-based DSL allows to write complex scenarios, which are impossible with some other competitors (for example, unpack a protobuf response and assert its elements)

- Impressive performance based on async Akka toolkit

It is great that Gatling offers a free open source version as well as paid for enterprise options. What sets Gatling apart from other leading performance testing tools is that it is extremely flexible and versatile as you can pretty much develop any logic to support your Gatling tests. Gatling is also continuously improving and coming out with new features which makes the tool even more powerful.

Some performance testers might not like Gatling because it is very dev oriented compared to other performance testing tools. It also doesn't support as many protocols as you'd get with HP's tooling.

Due to it's versatility, we are able to use Gatling to carry out all of our performance testing needs. We have very complex user journeys that are run at extremely high volumes and we wouldn't be able to carry out these tests if it wasn't for Gatling.