G2

Raman B.

Architect, Quality Engineering

Mid-Market (51-1000 emp.)

9/15/2026

"Gatling Java DSL: Maintainable Load Tests, Excellent Reports, and Seamless CI/CD"

4/5

What do you like best about Gatling?

Gatling's Java DSL is the standout feature — writing load test scenarios in code means tests live in Git, get peer-reviewed, and stay maintainable long-term. We built a shared internal library (gatlingcommon) of reusable feeders, load patterns, and helpers that any team can import and use in minutes, which has dramatically reduced onboarding time for new load test projects.

The built-in HTML reports are clean and actionable — per-request percentile breakdowns, throughput charts, and response time distributions are generated out of the box with zero dashboard setup, cutting post-run analysis time significantly.

CI/CD integration is seamless — the Maven plugin fits naturally into Jenkins pipelines, giving fine-grained control over simulation execution and report generation.

Performance-wise, Gatling is exceptionally efficient. A single node can simulate thousands of virtual users with minimal resource consumption.

Pricing is a strong ROI story for open-source users — the core tool is free, and the ecosystem is mature enough to cover most enterprise load testing needs.

The community forum is active, and the documentation is thorough. Onboarding a new team member to write their first simulation takes a day, not a week. Review collected by and hosted on G2.com.

What do you dislike about Gatling?

The biggest limitation is distributed load testing: the open-source version offers no supported way to merge binary simulation logs from multiple nodes into a single consolidated report. Starting with Gatling 3.11.x, the simulation log format changed to binary, which makes manual log merging impossible. In 3.10.x, manually merging logs was a workable workaround, but that option is no longer available. As a result, teams running distributed tests are pushed to either stay on older versions or move to Gatling Enterprise.

Support for the open-source version is community-driven only. When you hit critical blockers, the official response is often along the lines of, “this is only supported in Gatling Enterprise.”

Reference: https://community.gatling.io/t/generate-gatling-report-from-multiple-simulation-log-files-with-version-3-13-5/9737 Review collected by and hosted on G2.com.

What problems is Gatling solving and how is that benefiting you?

Gatling solves the problem of realistic, high-volume load testing in a developer-friendly way. By providing a code-first DSL in Java, it allows us to write load test scenarios that are version-controlled, peer-reviewed, and reusable — treating performance tests as first-class code rather than throwaway scripts.

The biggest benefit has been standardization across teams. We built a shared internal library of reusable load patterns, feeders, and helpers that any team can import, which means a new load test project can be up and running in minutes instead of days.

Gatling also solves the reporting problem — generating detailed HTML reports with per-request percentile breakdowns, throughput, and response time distributions out of the box means we spend less time building dashboards and more time acting on results.

On the CI/CD side, the Maven plugin integrates cleanly into Jenkins pipelines, making it easy to run performance tests as part of our regular release process rather than as a manual afterthought.

Overall, Gatling has shifted load testing from a specialist activity to something any developer on our team can contribute to. Review collected by and hosted on G2.com.