--- title: Gatling Reviews meta_title: 'Gatling Reviews 2026: Details, Pricing, & Features | G2' meta_description: Filter 92 reviews by the users' company size, role or industry to find out how Gatling works for a business like yours. aggregate_rating: rating_value: 4.4 review_count: 92 scale: '5' date_modified: '2026-08-08' parent_category: name: Development url: https://www.g2.com/categories/development --- # Gatling Reviews **Vendor:** Gatling **Category:** [Load Testing Tools](https://www.g2.com/categories/load-testing-tools) **Average Rating:** 4.4/5.0 **Total Reviews:** 92 ## About Gatling Gatling is a load-testing solution that helps organizations identify bottlenecks and guarantee website stability under traffic load through test automation. Gatling Enterprise includes advanced features for reporting (live reporting, TCP connections metrics, bandwidth usage, injectors' monitoring) and automation (public APIs, new Continuous Integration plugins, clustering mode). With 16,000,000 downloads for more than 100 000 companies worldwide, Gatling’s solution is used in diverse industries such as software, e-commerce, streaming media, banking, insurance, gaming, and finance. ## Gatling Pros & Cons **What users like:** - Users value the **automation capabilities** of Gatling, enabling efficient load testing and seamless integration with CI/CD workflows. (2 reviews) - Users appreciate the **ease of use** of Gatling, enhancing automation and integration in their testing processes. (2 reviews) - Users value the **excellent customer support** from Gatling, enhancing their overall testing experience and satisfaction. (1 reviews) - Users value the **excellent customer support** from Gatling, enhancing their testing experience and troubleshooting efficiency. (1 reviews) - Users value the **easy setup** of Gatling, facilitating seamless integration with modern CI/CD pipelines for efficient testing. (1 reviews) - Flexibility (1 reviews) - Helpful (1 reviews) - Load Testing (1 reviews) - Simulation (1 reviews) - Time-saving (1 reviews) **What users dislike:** - Users find the **learning curve challenging** for non-developers due to Gatling's Scala-based DSL complexity. (1 reviews) - Users find Gatling's **insufficient documentation** and occasional bugs frustrating, affecting the overall usability and experience. (1 reviews) - Users find Gatling's **documentation lacking** , often encountering confusing information that complicates their experience. (1 reviews) - Users find the **poor UI** of Gatling challenging, especially for those without programming knowledge. (1 reviews) ## Gatling Reviews ### 1. Efficient Load Testing with Informative Reports **Rating:** 4.0/5.0 stars **Reviewed by:** Yessinkcharem@gmail.com Y. | software engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** August 04, 2026 **What do you like best about Gatling?** I use Gatling for performance tests of my microservices and find it easy to write load scenarios with minimal code. The reports generated are well-written, featuring charts that help quickly identify issues. The charts and reports are especially valuable for analysis, as I can easily see response time distribution and error rates, which makes it easier to pinpoint where the system is slowing down. The initial setup was fast and easy, thanks to the documentation. **What do you dislike about Gatling?** I find the learning curve can be slow because I'm not used to the Scala programming language. Things like chaining requests with dynamic data extraction, conditional logic within a scenario, or coordinating multiple users with different behaviors pose challenges for me. **What problems is Gatling solving and how is that benefiting you?** I use Gatling for performance tests, validating system capacity against real-world traffic. It helps identify bottlenecks swiftly and the generated reports make analysis easier, allowing quick insights into performance issues. ### 2. Reliable, Scalable Load Testing with Code and CI/CD Integration **Rating:** 4.5/5.0 stars **Reviewed by:** Sumit D. | QA Engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** July 15, 2026 **What do you like best about Gatling?** What I like most about Gatling is its ability to create realistic, scalable load tests using code. Because the test scenarios are written in code, they’re easy to version control, review, and integrate into CI/CD pipelines. As a result, performance testing becomes a natural part of the development process, rather than something that only happens right before a release. **What do you dislike about Gatling?** One area where Gatling could improve is the learning curve for new users. While the code-based approach is powerful and flexible, it can feel intimidating for testers without a programming background. More beginner-friendly tutorials, ready-to-use templates, and guided setup options would make onboarding smoother and less time-consuming. The reporting is comprehensive, but I’d like to see more interactive dashboards and built-in trend analysis to compare performance across multiple test runs without having to rely on external tools. Integration with popular observability platforms is possible, but the setup can sometimes involve extra configuration steps that could be simplified. From a UI perspective, there’s also room to make navigation and test management more intuitive, especially on larger projects. It would be helpful to add more AI-powered capabilities as well, such as automatic bottleneck detection, test scenario recommendations, or suggestions for optimizing load tests based on previous runs. Overall, these feel like opportunities for enhancement rather than major drawbacks. Gatling has been reliable and performs well for large-scale load testing, but improvements in usability and analytics would make it even more accessible and productive. **What problems is Gatling solving and how is that benefiting you?** Before adopting Gatling, performance testing was largely a manual effort and typically happened late in our release cycle. That timing made it hard to spot scalability issues early, and tracking down performance bottlenecks often required a lot of time and coordination. With Gatling, we’ve been able to automate load and stress tests and integrate them into our CI/CD pipeline, so we can validate application performance with every major release. This shift has helped us catch performance regressions sooner, improve stability under peak traffic, and go into deployments with more confidence. The detailed reports and metrics have also cut down the time needed to review and interpret results, which makes it easier for developers and QA engineers to work together on targeted performance improvements. As a result, we’ve shortened our performance testing cycle, lowered the risk of production issues during high-traffic periods, and delivered more reliable applications to our users. Overall, Gatling has made performance testing more consistent, repeatable, and efficient, and it provides a strong return on the time we invest in building automated test scenarios. ### 3. Gatling’s Code-First Performance Testing Fits Perfectly into Our Workflow **Rating:** 5.0/5.0 stars **Reviewed by:** Andrii O. | Senior QA Automation Engineer, Enterprise (> 1000 emp.) **Reviewed Date:** July 29, 2026 **What do you like best about Gatling?** I like best about Gatling is its code-first approach to performance testing. Test scenarios are written as maintainable code, which makes them easier to review, version, refactor, and integrate into a regular development workflow. **What do you dislike about Gatling?** the initial learning curve. The DSL is elegant once you understand it, but engineers without experience in Scala or functional programming concepts may find the syntax and error messages less approachable than JMeter’s graphical interface. Also we need more steps to set everything up to work with Scala. However, it is possible to choose Kotlin or Java instead. **What problems is Gatling solving and how is that benefiting you?** Gatling solves the problem of creating maintainable and repeatable performance tests for APIs and web applications. It allows performance scenarios, workload models, test data, checks, and assertions to be defined as code and stored together with the application or test project. Compared with GUI-based tools such as JMeter, Gatling makes collaboration through Git more practical. Changes are easier to review, merge, and track, especially when the performance test suite becomes larger and more complex. It is possible to execute Gatling from Ci CD pipelines and collect the results automatically ### 4. Gatling Makes Performance Testing Efficient with Flexible, CI/CD-Friendly Workflows **Rating:** 5.0/5.0 stars **Reviewed by:** Muhammed Sameer S. | Automation Tester (QA Engineer), Small-Business (50 or fewer emp.) **Reviewed Date:** July 27, 2026 **What do you like best about Gatling?** What I like most about Gatling is how easy it is to create and maintain performance tests. As an automation tester, I find its code-based approach more flexible than record-and-playback tools. It integrates smoothly with CI/CD pipelines, generates clear and detailed reports, and helps identify performance issues quickly. Overall, it's a reliable tool that makes performance testing efficient and fits well into modern automation workflows. **What do you dislike about Gatling?** One thing I dislike about Gatling is that it has a bit of a learning curve, especially if you're new to Scala or its scripting syntax. Creating complex test scenarios can take more effort compared to some GUI-based tools. Also, debugging scripts isn't always straightforward, and some advanced features require extra setup. That said, once you're familiar with it, the flexibility and performance make it worth using. **What problems is Gatling solving and how is that benefiting you?** Gatling helps us identify performance bottlenecks before applications go live by simulating real user traffic and measuring how the system behaves under load. As an automation tester, it gives me confidence that new features can handle expected traffic without affecting performance. It also helps catch issues early in the development cycle, supports continuous testing through CI/CD integration, and provides detailed reports that make it easier to analyze results and share insights with the team. ### 5. A flexible tool for building complex performance tests **Rating:** 5.0/5.0 stars **Reviewed by:** Marek S. | Senior QA Engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** July 23, 2026 **What do you like best about Gatling?** What I like most about Gatling is its flexibility and the ability to build complex performance test scenarios as code. It gives me full control over test flows, dynamic data, request generation, and different load injection models. I particularly appreciate that Gatling can be extended beyond standard HTTP testing. In my case, I use it for complex SOAP-based scenarios with dynamic request generation, WS-Security signing, custom mock services, and multi-step transaction flows. The Java-based DSL also makes it easier to structure, maintain, and reuse test components compared to traditional GUI-based performance testing tools. Another strong point is the clear separation between test logic, request generation, and load profiles, which makes the test project easier to develop and integrate into CI/CD pipelines. **What do you dislike about Gatling?** There is not much I dislike about Gatling itself. One challenge is that more complex or non-standard use cases can require additional custom development and a deeper understanding of the underlying technologies. For example, working with SOAP, WS-Security, or custom mock services requires building some functionality yourself. However, this is also a consequence of Gatling's flexibility, as it gives you the freedom to implement scenarios that go beyond typical HTTP/REST performance testing. **What problems is Gatling solving and how is that benefiting you?** Gatling helps us validate the performance and stability of our systems under different load conditions before changes reach production. It allows us to simulate realistic, multi-step transaction flows and control how the load is generated, from gradual ramp-up to sustained concurrency and peak-load scenarios. The main benefit is repeatability and automation. Performance tests can be maintained as code, reused across different scenarios, and integrated into CI/CD processes. This makes it easier to identify performance bottlenecks, compare system behavior between releases, and reproduce specific load conditions when investigating performance issues. **Official Response from Diego Salinas:** > Thank you for the thoughtful review, and especially for calling out our CI/CD integrations with Jenkins, GitLab, and GitHub Actions. Helping teams catch performance regressions before they hit production, especially ahead of high-stakes events like Black Friday, is exactly what we're aiming for. We also appreciate the feedback on the learning curve for non-developers. Since you last reviewed us, we've made this a priority. We launched a Recorder that lets you generate Gatling scripts from recorded actions rather than writing the Scala code by hand, plus AI-powered migration tools to help teams move existing JMeter and LoadRunner test suites into Gatling. We've also rolled out AI-powered documentation to make it easier to get unstuck without needing deep Scala expertise. Together, these are meant to lower exactly the barrier you described. We'd love for you to try them out and let us know how they compare to your experience so far. Thanks again for using Gatling and for the detailed feedback. ### 6. Developer-Friendly with Powerful Graphical Reporting **Rating:** 4.5/5.0 stars **Reviewed by:** Rishav . | Assistant System Engineer-trainee, Enterprise (> 1000 emp.) **Reviewed Date:** July 22, 2026 **What do you like best about Gatling?** I used Gatling for load testing REST APIs in one of my projects. I find it very lightweight, which makes handling concurrency from a single machine much easier. Compared to tools like JMeter, Gatling consumes fewer resources, which is beneficial for simulating millions of users, like during a Black Friday sale, saving a chunk of money on resources. It's developer-friendly, which I appreciate since version control with development is easy. I also like its reporting features, especially the graphical representations, as they provide a clear view of performance metrics. **What do you dislike about Gatling?** I find it challenging to learn Scala, which can be quite difficult for new folks who need to invest a lot of time. I feel Gatling's free tier is less flexible compared to open-source tools like JMeter that give you more ease to scale in the way you want. Setting up the Scala environment was somewhat difficult. **What problems is Gatling solving and how is that benefiting you?** I use Gatling for its lightweight and developer-friendly nature, which eases handling high concurrency with less infrastructure. It's valuable for cost-effective load testing, especially with its graphical reporting that enhances insights. **Official Response from Diego Salinas:** > thank you for the detailed review and for sharing how you're using Gatling for high-concurrency load testing! We're glad the lightweight design and graphical reporting are pulling their weight, especially for something as demanding as a Black Friday-scale simulation. Cost-effective load testing at that volume is exactly the problem we built Gatling to solve, so it's great to hear it's landing that way for you. On the Scala learning curve: that's fair feedback we hear often, and it's actually already changed. Gatling now supports Java, JavaScript, TypeScript, and Kotlin in addition to Scala, so you (or teammates who'd rather not pick up Scala) can write simulations in a language you already know. Worth a look if that setup friction was the main blocker. On the free tier: we're always weighing flexibility against sustainability for the open-source project, so I've passed your feedback to the product team. Thanks again for taking the time to write this up. If you get a chance to try one of the newer language SDKs, we'd love to hear how it goes. Diego from Gatling ### 7. Realistic Load Testing with Rich Metrics and CI/CD-Friendly Scripting **Rating:** 4.0/5.0 stars **Reviewed by:** Minaz K. | QA Consultant, Small-Business (50 or fewer emp.) **Reviewed Date:** July 22, 2026 **What do you like best about Gatling?** What I like best about Gatling is its ability to simulate realistic user loads and provide detailed performance metrics. Being code-based, it allows test scripts to be version-controlled and integrated easily into CI/CD pipelines. I also appreciate its rich reports and dashboards, which help quickly identify performance bottlenecks and analyze system behavior under load. **What do you dislike about Gatling?** What I dislike about Gatling is that it is less beginner-friendly than GUI-based performance testing tools. Since it is code-centric, it requires programming knowledge and can take more effort to create, debug, and maintain complex test scenarios. **What problems is Gatling solving and how is that benefiting you?** Gatling solves the challenge of validating an application's performance, scalability, and stability under different user loads before issues impact production. It helps identify bottlenecks such as slow response times, resource constraints, and throughput limitations by simulating realistic user traffic. For me, the main benefit is the ability to proactively detect performance issues early in the development lifecycle. This helps improve application reliability, supports performance validation in CI/CD pipelines, and provides valuable insights through detailed reports, enabling teams to deliver a better user experience and reduce production risks. ### 8. Effortless Performance Testing with Gatling **Rating:** 4.5/5.0 stars **Reviewed by:** Vishal R. | Software Development Engineer in Test II, Enterprise (> 1000 emp.) **Reviewed Date:** July 15, 2026 **What do you like best about Gatling?** I love how Gatling helps us generate different types of load while keeping test scripts maintainable. The Gatling reports are detailed and make it simple to identify performance bottlenecks. I also appreciate that it easily integrates with Jenkins pipelines, which is really useful for our deployment in a Kubernetes environment. Gatling's feature for generating real-time different load scenarios helps us catch performance issues before they reach production. Maintaining scripts in Gatling is easy, it requires minimal infrastructure, and it's straightforward to learn for anyone with programming knowledge. Setting up Gatling was straightforward by following the Gatling documentation. **What do you dislike about Gatling?** If we can integrate Gatling reports with application performance management tools like Grafana. **What problems is Gatling solving and how is that benefiting you?** I use Gatling to test backend APIs performance under peak load, assess response times, and decide infrastructure for microservices. It generates various load scenarios, helps catch issues before production, keeps scripts maintainable, provides detailed reports for bottlenecks, and integrates easily with Jenkins pipelines. ### 9. Reliable and Efficient Load Testing Tool for Modern CI/CD Pipelines **Rating:** 4.5/5.0 stars **Reviewed by:** Neema F. | Full Stack Engineer, Small-Business (50 or fewer emp.) **Reviewed Date:** July 31, 2026 **What do you like best about Gatling?** Gatling is how efficiently it handles high-load performance testing without consuming excessive system resources, especially compared to other load testing tools I've used. The Scala-based DSL makes it easy to write clear, maintainable test scenarios. It also integrates smoothly into our CI/CD pipeline, so we can catch performance regressions before they reach production **What do you dislike about Gatling?** Scala knowledge required for scripting. Debugging complex scenarios can be tricky **What problems is Gatling solving and how is that benefiting you?** Gatling helps us identify performance bottlenecks and validate system stability before releasing new features into production. By simulating realistic load scenarios, we can catch issues like slow response times. This has helped us build more confidence in our releases, reduce the risk of downtime during peak usage, and make more informed decisions about scaling infrastructure. Overall, it's saved us from costly post-release fixes and given the team a clearer picture of how our systems perform under real-world conditions. ### 10. Flexible, Coding-First Performance Testing with Clear, Intuitive Reports **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Hospital & Health Care | Mid-Market (51-1000 emp.) **Reviewed Date:** June 21, 2026 **What do you like best about Gatling?** What I like most about Gatling is the flexibility and freedom it gives you when designing performance tests. It makes it easy to create reusable scenarios, build complex test chains, and structure tests in a maintainable way. The ability to use a real programming language such as Kotlin is a major advantage, as it allows for advanced logic and customization that would be difficult to achieve with more restrictive tools. This gives me full control over how I design, organize, and execute my tests. I also appreciate how clear and intuitive the reporting is. The reports are easy to understand and communicate to both technical and non-technical stakeholders. Overall, the coding-first approach and the level of control it provides are what make Gatling stand out for me. **What do you dislike about Gatling?** One area where Gatling could improve is troubleshooting and error analysis. The reports do not always provide enough detail about failed requests, which can make investigations more difficult. For example, when a request returns an HTTP 500 error, it would be helpful to see the underlying error message or stack trace directly in the report instead of having to search through application logs. Having more detailed failure information available out of the box would make debugging and root-cause analysis much faster and more efficient. **What problems is Gatling solving and how is that benefiting you?** The main problems Gatling solves for me are performance regression control and load testing under realistic conditions. It helps detect whether a new update has negatively impacted API performance, such as increased response times or reduced throughput, which is crucial for maintaining stability in production. Another key benefit is the ability to simulate different load scenarios on various machine specifications. This makes it possible to evaluate how systems behave under stress and identify potential bottlenecks or scaling issues before they affect real users. Overall, Gatling provides valuable insight into performance trends and system reliability over time. **Official Response from Diego Salinas:** > Thanks so much for taking the time to share this. We’re really happy to hear Gatling is giving you the control and clarity you need in your testing workflow. Your point on debugging is fair, too. Making failure analysis faster and easier is exactly the kind of feedback that helps us improve the product. Thanks again for the thoughtful review. ### 11. Excellent Documentation and Broad Language Support **Rating:** 4.5/5.0 stars **Reviewed by:** Damaso F. | QA Engineer, Small-Business (50 or fewer emp.) **Reviewed Date:** July 18, 2026 **What do you like best about Gatling?** I like the documentation and the many languages it supports; it gives me flexibility across multiple projects. **What do you dislike about Gatling?** It’s hard to think of something I dislike, but if I had to mention one thing, it would be that the generated reports could be more user-friendly and easier for anyone to understand at first sight. **What problems is Gatling solving and how is that benefiting you?** In the project where I used it, it handled the performance-testing part in an easier way by letting us write code. Before, we used other tools like JMeter, but we prefer this one because it integrates what we already know about coding into performance testing. ### 12. Effortless Integration and User-Friendly Documentation **Rating:** 4.5/5.0 stars **Reviewed by:** pratik r. **Reviewed Date:** July 20, 2026 **What do you like best about Gatling?** I found Gatling easy to understand and write code in. Even when I joined the project without knowing anything about Gatling, the inbuilt repository with the code and framework was easy to comprehend. The code is in a very readable format, so anyone with some technical knowledge can read, understand, and write it. The documentation on the Gatling site is pretty self-explanatory, making it straightforward to learn anything new and implement Gatling code in services. Working with Gatling was really good because of this easy-to-read and follow documentation. The initial setup was also easy, with top-notch documentation that anyone can follow. **What do you dislike about Gatling?** Not anything to say at this stage **What problems is Gatling solving and how is that benefiting you?** I use Gatling for performance testing. It's easy to understand and write code, even for newcomers. The documentation is self-explanatory, aiding quick setup and implementation. ### 13. Easy Load Testing with Gatling, Needs Better Server-Side Features **Rating:** 4.5/5.0 stars **Reviewed by:** dmytro s. | Mid-Market (51-1000 emp.) **Reviewed Date:** July 15, 2026 **What do you like best about Gatling?** I like Gatling for its usability and simplicity compared to other tools like JMeter. The multithreading and automation capabilities are particularly beneficial, allowing me to set up each thread with ease and perform a lot of actions. It was great for handling load testing without being overly complicated, which made tasks much easier to manage. The initial setup was quite easy and took less than a day. **What do you dislike about Gatling?** I don't think Gatling was able to run on the server as a watchdog or for deploying tests for stress and load testing. Also, I don't remember if Gatling had the option to run load tests while deploying on CICD. **What problems is Gatling solving and how is that benefiting you?** I use Gatling for blog and API testing to see how applications behave under different load conditions, particularly for stress and load testing. ### 14. Highly Customizable DSLs with Strong Community Support **Rating:** 4.5/5.0 stars **Reviewed by:** Nilson N. | Ssr Adv Test Automation Enginner, Mid-Market (51-1000 emp.) **Reviewed Date:** July 21, 2026 **What do you like best about Gatling?** The ability to customize the validations and the ability to integrate as a DSL in different programming languages. The broad community is fundamental when it comes to select it since you can find solutions to most of challanges from people in the past already. **What do you dislike about Gatling?** The HTML report is hard to modify; we have to depend on a cloud solution, which, for a small project, is not feasible. **What problems is Gatling solving and how is that benefiting you?** Ability to customize and create so detailed validations during performance testing, and the ability to incorporate additional programming dependencies to enrich your validation. When it comes to E2E performance testing, we can find so many flavours in user flows, and those features of Gatling give you the ability to adapt the tool to so many user flows and technologies ### 15. Flexible Cloud Setup That Fits Every Team **Rating:** 5.0/5.0 stars **Reviewed by:** Matt P. | QA Lead, Enterprise (> 1000 emp.) **Reviewed Date:** March 09, 2026 **What do you like best about Gatling?** Flexibility. I like to write in Scala, others prefer Kotlin, Frontend and QA colleagues prefer TypeScript or Javascript. All as code, all in cloud. Perfect setup for current times **What do you dislike about Gatling?** Setting up the internal network runners is not ideal, but nothing overcomplicated **What problems is Gatling solving and how is that benefiting you?** Gatling is helping us solve two main problems. First, it removes the ceiling we hit with local testing. When we run tests locally, we’re limited by how many users a workstation can handle, which is usually not enough to understand real scaling behavior (at least with Java; with Scala it’s much better). With Gatling Enterprise, we can safely push tests into the thousands of users and see how our systems actually behave under load. Second, it gives us a controlled way to stress critical user paths so we can validate autoscaling and overall system stability. The biggest benefit isn’t the report itself, but the engineering signal: whether the service stays healthy, whether scaling kicks in correctly, and where it breaks as load increases. With Gatling cloud, we also have the option to run tests from external networks or private IPs, which is great for validating the end-to-end user journey. **Official Response from Diego Salinas:** > Hi Matt, thank you for the detailed review! We're glad the language flexibility and cloud setup are working well for your team. That polyglot workflow is exactly what we designed for, so it's good to hear it's landing that way in practice. And it's great that Gatling Enterprise is helping you get past the local-testing ceiling and giving your team a clear picture of autoscaling and stability under load. That's the part we care most about. Thanks for flagging the internal network runner setup, too. Onboarding steps like that are exactly where we're trying to smooth things out, and specific feedback like yours helps us decide where to focus next. Appreciate you taking the time to write this up in such detail. It's genuinely useful for us, and for other teams weighing up Gatling. Diego from Gatling ### 16. Reliable, resource-efficient stress testing for high-volume booking engines **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Transportation/Trucking/Railroad | Mid-Market (51-1000 emp.) **Reviewed Date:** August 08, 2026 **What do you like best about Gatling?** In my QA role, I relied heavily on Gatling to stress-test our core vehicle-booking flows. The standout feature for me was Gatling’s code-as-configuration DSL. Since we could write load tests as code, we kept them in version control right alongside the application code. That shift changed our workflow significantly and saved our QA team hours of manual test maintenance each week, especially compared with UI-heavy legacy tools. Another benefit I didn’t expect at first was how smoothly Gatling fit into our existing CI/CD pipelines. It didn’t just enable large, concurrent stress tests; it also gave us immediate, automated performance feedback on new deployments. On top of that, the out-of-the-box HTML reporting is excellent—it helped us quickly pinpoint specific database bottlenecks during high-traffic booking simulations without needing to set up external visualization dashboards. **What do you dislike about Gatling?** While the code-as-configuration approach is a strength, the steep learning curve of Gatling's Scala-based DSL was our biggest hurdle. During our Europcar booking stress tests, onboarding QA engineers who were used to visual, GUI-based tools (like JMeter) took significantly longer. The impact was a slower initial setup phase for our load-testing framework, as team members had to learn a new language syntax just to write basic tests. A potential improvement would be offering a lightweight, visual test-builder interface for simpler scenarios, which would lower the barrier to entry while keeping the powerful code DSL for complex edge cases. **What problems is Gatling solving and how is that benefiting you?** Before using Gatling at Europcar, we struggled to accurately simulate high-volume, concurrent user traffic on our booking engine without consuming massive amounts of hardware resources. Our previous testing tools were difficult to integrate into an automated CI/CD pipeline, making performance testing a slow, manual bottleneck before major releases. Now, we can write our load tests as code and automatically trigger them within our deployment pipeline, which has resulted in much faster, automated feedback loops. The primary benefit is that we reliably catch database deadlocks and API latency issues early. Quantifiably, this has resulted in a roughly 30% reduction in time spent configuring performance tests, and it has significantly increased the reliability of our booking platform during peak holiday traffic spikes ### 17. Easy Jenkins Integration and Detailed Reports for Reliable Performance Testing **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Events Services | Mid-Market (51-1000 emp.) **Reviewed Date:** August 06, 2026 **What do you like best about Gatling?** Gatling has been easy to integrate into our Jenkins pipeline, making performance testing an automated part of our release process. I also like the detailed reports, which make it simple to analyze response times and identify bottlenecks. The scripting approach gives us flexibility to maintain and update test scenarios as our application evolves, and overall it has been a reliable tool for our performance testing needs. **What do you dislike about Gatling?** The initial learning curve is probably the biggest drawback, especially for team members who are new to Gatling's scripting approach. Creating and maintaining complex test scenarios can take some time to get used to. While the documentation is helpful, I'd appreciate more real-world examples and troubleshooting guides for advanced use cases. Apart from that, the tool has been reliable for our performance testing needs. **What problems is Gatling solving and how is that benefiting you?** Gatling helps us validate our application's performance before every release by automating load tests through Jenkins. It enables us to identify performance bottlenecks, detect regressions early, and ensure critical user flows remain stable under load. This has improved our release confidence and made performance testing a consistent part of our CI/CD process. ### 18. Reliable Performance Testing for Micro services APIs **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Retail | Enterprise (> 1000 emp.) **Reviewed Date:** August 04, 2026 **What do you like best about Gatling?** I was able to handle performance testing at scale while keeping the test scripts clean and maintainable. The developer friendly method using code based scenarios made it easier to version, review, and collaborate on tests compared to GUI tools. **What do you dislike about Gatling?** We need more beginner friendly documentation, examples, that would make it more accessible for new users. There can be a learning curve for users who are more familiar with traditional GUI based performance testing tools **What problems is Gatling solving and how is that benefiting you?** Gatling helped us validate the performance, scalability, and reliability of our microservice APIs by simulating realistic user loads and identifying potential bottlenecks. We used Gatling along with a BDD approach using Karate to test APIs, including scenarios that interact with the reporting service in a pharmacy management system. Tested how our sites handle expected traffic, maintain response time targets, and remain stable under load. This helped our team identify issues faster, improve API efficiency, and deliver a more reliable experience for end users. ### 19. Developer-Friendly with a Learning Curve **Rating:** 3.5/5.0 stars **Reviewed by:** Verified User | Small-Business (50 or fewer emp.) **Reviewed Date:** July 28, 2026 **What do you like best about Gatling?** I like that Gatling is a non-GUI, developer-centric tool. The fact that scripts can even be AI-generated is pretty cool, and I find the memory footprint per script to be actually minuscule. It's efficient enough that I can use a single VM to run over 500 threads. I also appreciate how Gatling can be integrated into our dev workflows, allowing Claude to auto-generate Gatling scripts as we develop and build APIs. Additionally, AI can go through Postman collections to create a complete Gatling suite of scripts. Setting up Gatling was rather easy, with no problems there. **What do you dislike about Gatling?** Since Gatling is non-GUI, I find it has a learning curve for us non-developers. It takes time for us to figure out the functions and features. Also, I face challenges because Gatling requires Scala, and I had to cross-train Java developers to read and understand Scala code. **What problems is Gatling solving and how is that benefiting you?** I use Gatling for scripting end-to-end business workflows, creating reusable templates, and scaling our performance testing frameworks. The low memory footprint allows running 500+ threads on a single VM. It integrates with our dev workflows for auto-generating scripts. ### 20. Lightweight, Fast, and Accurate Testing with Gatling **Rating:** 4.5/5.0 stars **Reviewed by:** Ravindra G. | Senior Test Engineer, Small-Business (50 or fewer emp.) **Reviewed Date:** July 21, 2026 **What do you like best about Gatling?** I like that Gatling is lightweight and easy to use. There are many options available for script preparation, which allows us to work fast and achieve accurate results. The initial setup was smooth, making it easier for us to transition to using Gatling for performance testing activities. **What do you dislike about Gatling?** We have an issue with the report file not being generated in Excel format. Instead, Gatling reports are provided in a different file format. It would be better if Gatling could generate reports in Excel format as well. **What problems is Gatling solving and how is that benefiting you?** I use Gatling for performance testing to solve production issues. It's lightweight and easy to use, with many script options. We work fast and get accurate results. ### 21. Seamless Karate Integration with Rich Performance Insights **Rating:** 5.0/5.0 stars **Reviewed by:** Vijaysai M. | Staff Quality Assurance Engineer, Small-Business (50 or fewer emp.) **Reviewed Date:** August 01, 2026 **What do you like best about Gatling?** It integrates well with my existing Karate framework. Can easily run load tests and produces reports with rich performance insights. **What do you dislike about Gatling?** Nothing much to add, really. It’s one of the best tools I’ve used so far for performance testing, and it has worked well for what I needed. **What problems is Gatling solving and how is that benefiting you?** It helps me simulate load on various services in our product, so I can measure performance and identify bottlenecks. ### 22. Gatling user since 2016 **Rating:** 5.0/5.0 stars **Reviewed by:** Boris K. | Senior Automation Engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** June 29, 2023 **What do you like best about Gatling?** Writing performance tests as a code, gradle support. Very good documentation and a very useful community. Great memory management, easy support of tens of thousands of users. **What do you dislike about Gatling?** I still haven’t found a perfect way to debug the tests yet. **What problems is Gatling solving and how is that benefiting you?** 1. Tens of thousands of users simulation 2. Groups of requests, simulating complex browser pages using the BE 3. Good visualization of load/stress test results ### 23. Great Load & Performance Testing Capabilities for Our Infrastructure **Rating:** 4.5/5.0 stars **Reviewed by:** Anurag A. | Engineering Manager, Enterprise (> 1000 emp.) **Reviewed Date:** August 07, 2026 **What do you like best about Gatling?** It has great capabilities and features for measuring load and performance when testing our infrastructure. **What do you dislike about Gatling?** Pricing is bit on a higher side and we have less community till date , we can have ways to onboard customer **What problems is Gatling solving and how is that benefiting you?** it helps me and my team to access the performance of our Web Applications , API's under immense load . ### 24. Great tool to Boost Legacy App Performance **Rating:** 4.5/5.0 stars **Reviewed by:** shivangi j. | Associate Developer, Mid-Market (51-1000 emp.) **Reviewed Date:** July 29, 2026 **What do you like best about Gatling?** Its really good tool for load testing tool i actually use it for my old legacy app and it really helped me to improve the app performance. **What do you dislike about Gatling?** It’s difficult for an end user to understand the UI, so it could be improved in that area to make it clearer and easier to use. **What problems is Gatling solving and how is that benefiting you?** We were struggling with performance issues in our app. Since the app was live and a legacy application, we were dealing with production issues on a daily basis. To address all of that, we decided to go with Gatling. ### 25. Efficient Performance Testing Made Easy **Rating:** 4.0/5.0 stars **Reviewed by:** Huzaifa V. | Enterprise (> 1000 emp.) **Reviewed Date:** August 03, 2026 **What do you like best about Gatling?** I like that Gatling made performance testing easy for my Kotlin backend application. It helped us achieve our tier1 project's SLA and identify crucial breaking points under stress testing. The tool's ease of use and the powerful in-built functionalities fit my use case perfectly. I appreciate how exceptionally it works to test systems in bottleneck traffic. Also, the initial setup was very easy and understandable. **What do you dislike about Gatling?** Nothing **What problems is Gatling solving and how is that benefiting you?** I use Gatling for stress testing, identifying application breaking points, with its ease of use and powerful functionalities helping us handle bottleneck traffic. ### 26. Gatling’s Fluent, Readable Test Scripting Is a Joy to Use **Rating:** 4.0/5.0 stars **Reviewed by:** Jakub D. | Principal Architect, Small-Business (50 or fewer emp.) **Reviewed Date:** March 31, 2026 **What do you like best about Gatling?** Gatling’s biggest strength, in my experience, is the developer experience when building test scripts. A lot of effort has clearly gone into the fluent style of writing tests, and even though the scenarios are written as code, they remain easy for humans to read and understand. **What do you dislike about Gatling?** There’s a lack of automatic correlation detection for test scripts, which makes the process more manual than it needs to be. **What problems is Gatling solving and how is that benefiting you?** I’ve integrated Gatling into my resilience testing framework, using Kafka along with other messaging protocols. Gatling’s core is highly efficient in terms of memory and overall resource management, which makes it a powerhouse load-testing platform and a strong foundation for expanding support across additional protocols. **Official Response from Diego Salinas:** > Thank you so much for the review, Kuba! We’re really glad the scripting experience feels clear and readable. That developer experience has always mattered a lot to us. We also appreciate the feedback on automatic correlation detection. Reducing manual work in script creation is a valuable point, and it’s helpful to hear where the workflow can be smoother. Thanks again for sharing how you’re using Gatling in resilience testing and messaging-based systems. ### 27. Intuitive with Strong Community Support, but Documentation Needs Improvement **Rating:** 5.0/5.0 stars **Reviewed by:** Marijana R. | Quality Assurance Engineer, Information Technology and Services, Mid-Market (51-1000 emp.) **Reviewed Date:** April 25, 2023 **What do you like best about Gatling?** I use Gatling for testing in both my previous and current company, and I really like their support. The switch from using Scala to TypeScript for writing tests has been a positive experience for me. The DSL (domain-specific language) that Gatling has is very intuitive, making it easy to use. I appreciate that it's easy to use, especially compared to tools like JMeter, and I like that you have something more tangible in the code form. The fact that developers can easily jump in and manage changes since it's code-based is great. I find the syntax clear, and the reporting feature is very user-friendly, providing a history of load tests that is quite helpful. The support for languages and clear syntax makes writing tests easier, even for people who might have never coded before. I also find the reporting crucial for quickly getting the information I need and spotting bottlenecks or slow requests at a glance. The feature that allows comparisons between different runs is something I appreciate very much. Additionally, the community support is great. I also recommended Gatling at my current company because I liked it. Setup is now easier thanks to moving from Scala to Java and TypeScript support, which I think helps in facilitating the setup. There's also a recording tool that can get you started quickly. I really like Gatling, think it's a great tool, and appreciate the great support from the community. **What do you dislike about Gatling?** I think maybe their documentation could be a bit more. It is good, but I think it could be improved. Sometimes, you get confusing information that might not be suitable for your case. I think that could be improved. Before, in my previous company, when I used their reporting, I had some bugs in terms of a layout break. If I have a long endpoint written, then the layout would break and basically make the report not useful to me. So I have to make workarounds there. **What problems is Gatling solving and how is that benefiting you?** Gatling is easier to use than tools like JMeter with its clear code form. It supports versioning and lets developers control changes. Its reporting is user-friendly, providing fast insights and helping spot bottlenecks quickly. ### 28. Rich Data Generators and Powerful Simulation Run Management **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Mid-Market (51-1000 emp.) **Reviewed Date:** April 28, 2026 **What do you like best about Gatling?** I like the flexibility I get in implementing data generators (feeders). This allows for representative and sufficiently random data that ultimately gives meaningful performance test results. I also like the simulation run management and history offered by the enterprise product which lets non-engineers to access and use the results directly. The technical documentation is an ever-evolving artifact but in its current state it is useful and well structured and helps newcomers create effective simulations, not just "hello world" versions. **What do you dislike about Gatling?** Some of our integrations (e.g. with Github workflows) are brittle, although I should add that they are improving both the integrations themselves and the relevant documentation. **What problems is Gatling solving and how is that benefiting you?** Infrastructure management (minimum viable configuration) Infrastructure budget projections Identification of throughput bottlenecks SLO monitoring Performance regression **Official Response from Diego Salinas:** > Thank you so much for the thoughtful review. It’s great to hear Gatling is helping your team create more realistic tests, share results more easily, and keep performance work connected to real engineering goals. We also appreciate your honest note on integrations. CI/CD reliability really matters, and feedback like this helps us keep improving both the product and the documentation. Thanks again for taking the time to share your experience with Gatling. ### 29. Effortless Test Case Creation Without the JMeter UI Hassle **Rating:** 5.0/5.0 stars **Reviewed by:** Godwin B. | Digital Transformation Lead, Enterprise (> 1000 emp.) **Reviewed Date:** July 18, 2026 **What do you like best about Gatling?** Creating test cases was a breeze, and I didn’t have to bother with a UI like JMeter. **What do you dislike about Gatling?** Scala documentation and support are sometimes inaccurate or not detailed enough. **What problems is Gatling solving and how is that benefiting you?** Load testing has been easier, especially thanks to the code-based load testing capabilities. It lets you adapt to requirements more easily without having to fiddle through UI components. ### 30. Incredible tool! **Rating:** 5.0/5.0 stars **Reviewed by:** Christophe H. | Consultant, Mid-Market (51-1000 emp.) **Reviewed Date:** July 15, 2026 **What do you like best about Gatling?** Gatling was really useful for me, and it completely changed the way I approach load testing. **What do you dislike about Gatling?** Honestly nothing, the tool is almost perfect **What problems is Gatling solving and how is that benefiting you?** Gatling eliminates the guesswork around performance bottlenecks. We catch scalability issues before they hit production, which saves us downtime and keeps our users happy. ### 31. Seamless Integrations and Great Out-of-the-Box Reports **Rating:** 4.0/5.0 stars **Reviewed by:** Deodato A. | DevOps Engineer (CI/CD & Secure SDLC) , Mid-Market (51-1000 emp.) **Reviewed Date:** April 12, 2026 **What do you like best about Gatling?** The integration with other tools, along with the out-of-the-box reports, is what I like most. **What do you dislike about Gatling?** When I first started using Gatling, it was only compatible with Scala, but that’s no longer the case. What I dislike most is that it isn’t fully open source. **What problems is Gatling solving and how is that benefiting you?** As part of our broader software performance metrics work, Gatling helped me fine-tune request rates and limits across different microservices. That, in turn, made it easier to reduce our overall cloud costs. **Official Response from Diego Salinas:** > Thank you so much for the review. We’re happy to hear Gatling’s integrations and reports have been useful in your performance work, especially when tuning microservices and keeping cloud costs under control. We also appreciate your note on open source. Gatling’s open-source roots are a big part of who we are, and we’ll keep listening to feedback from the community as the product evolves. Thanks again for sharing your experience with Gatling. ### 32. Gatling Enterprise API Streamlines Load Testing and Scheduling **Rating:** 5.0/5.0 stars **Reviewed by:** Bian J. | Principal Software Engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** January 30, 2026 **What do you like best about Gatling?** Gatling and the Gatling Enterprise API streamlines our load testing development and scheduling flow. We were able to build a command line tool to automate the simulation scheduling flow so that our developers could iterate fast. **What do you dislike about Gatling?** I think more code examples, especially completed projects could be really helpful for users to understand the expected usage of certain features. **What problems is Gatling solving and how is that benefiting you?** We use Gatling and Gatling Enterprise to write and run simulations which help us load test our backend services so that we are ready for big events of the year such as Black Friday / Cyber Monday. **Official Response from Diego Salinas:** > Hi Bian, thank you for sharing this! It's great to hear the Gatling Enterprise API helped you build a CLI tool for automating simulation scheduling. That kind of fast iteration loop is exactly what we built the API for, so it's rewarding to see it used that way. And knowing it's helping you prep for high-stakes events like Black Friday and Cyber Monday makes it even better. Your point on code examples and complete sample projects is well taken. A full, working example often saves more time than reading the docs feature by feature, so this is useful input as we keep expanding what we share. Thanks again for the detailed feedback, and for being a Gatling user. Diego from Gatling ### 33. Highly Functional Tool for Performance Testing **Rating:** 4.5/5.0 stars **Reviewed by:** Ankit K. | Small-Business (50 or fewer emp.) **Reviewed Date:** March 18, 2026 **What do you like best about Gatling?** I use Gatling for performance testing and I really like its functionality and reports. It's been good for all aspects so far. The initial setup was easy too, which was a plus. **What do you dislike about Gatling?** Nothing **What problems is Gatling solving and how is that benefiting you?** Gatling helps me assess the performance of my APIs with its functionality and reports, which I find very valuable. **Official Response from Diego Salinas:** > Thank you for sharing your positive experience with Gatling! We're thrilled to hear that you find it highly functional for performance testing and appreciate its ease of setup. It's great to know that the tool is helping you assess the performance of your APIs effectively. If you ever have any questions or need assistance with Gatling in the future, please don't hesitate to reach out. We're here to support you every step of the way. Diego from Gatling ### 34. Gatling: the powerful, efficient performance tool ready for CI/CD **Rating:** 5.0/5.0 stars **Reviewed by:** Evelyn Daniela M. | Senior Software Quality Engineer, Small-Business (50 or fewer emp.) **Reviewed Date:** June 05, 2025 **What do you like best about Gatling?** 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 do you dislike about Gatling?** 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. **What problems is Gatling solving and how is that benefiting you?** 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. **Official Response from Diego Salinas:** > Hi Bian, thank you for sharing this! It's great to hear the Gatling Enterprise API helped you build a CLI tool for automating simulation scheduling. That kind of fast iteration loop is exactly what we built the API for, so it's rewarding to see it used that way. And knowing it's helping you prep for high-stakes events like Black Friday and Cyber Monday makes it even better. Your point on code examples and complete sample projects is well taken. A full, working example often saves more time than reading the docs feature by feature, so this is useful input as we keep expanding what we share. Thanks again for the detailed feedback, and for being a Gatling user. Diego from Gatling ### 35. A large-scale tool, easy to use and integrate into the testing cycle. **Rating:** 5.0/5.0 stars **Reviewed by:** Rodrigo Antonio C. | Software Testing Expert Partner, Enterprise (> 1000 emp.) **Reviewed Date:** June 05, 2025 **What do you like best about Gatling?** 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 - Support for different programming languages - Easy-to-understand and learn documentation - Open source with an easy-to-use injection platform - Integration in CI/CD **What do you dislike about Gatling?** Although I don't have many remarks, I would like to see the integration with Grafana resumed and the addition of more open-source protocols for the community. **What problems is Gatling solving and how is that benefiting you?** One of the major problems Gatling has helped me with is creating realistic simulations and scenarios to detect bottlenecks across multiple flows in the banking and e-commerce sectors. With its dynamic and easy-to-interpret reports, I can identify issues and request queuing (REST) from the client side. **Official Response from Diego Salinas:** > Hi Rodrigo, thank you for this thoughtful review! It means a lot to hear that Gatling has stayed your go-to tool over time, and that the recorder, reporting, and CI/CD integration are still holding up well for large-scale testing. It's also great to know Gatling is helping you catch bottlenecks and queuing issues across banking and e-commerce flows: those are exactly the high-stakes environments where catching problems early matters most. Thanks for the notes on Grafana integration and open-source protocol support too. Both are good signals for us on where the community would like to see more investment, and we'll make sure this feedback gets to the right team. Really appreciate you taking the time to write this, and for being such a long-time user. ### 36. Great to use for performance and QA Automation **Rating:** 4.0/5.0 stars **Reviewed by:** OMER Y. | Sr. Software Developer, Small-Business (50 or fewer emp.) **Reviewed Date:** March 07, 2023 **What do you like best about Gatling?** I really like how Gatling has strengthened its integration with modern CI/CD pipelines, such as Jenkins, GitLab, and GitHub Actions. The ability to seamlessly automate performance tests within DevOps workflows ensures performance benchmarks are met before deployment, which is crucial for high-traffic events like product launches or Black Friday sales. This makes Gatling a go-to for teams aiming for continuous quality. **What do you dislike about Gatling?** Learning Curve for Non-Developers: Gatling’s Scala-based DSL (Domain-Specific Language) is expressive but can be challenging for testers without programming experience. Improving the documentation with more beginner-friendly tutorials or introducing a GUI-based test recorder (like JMeter’s) could make it more accessible to non-coders, broadening its user base. **What problems is Gatling solving and how is that benefiting you?** To automate the software testing, we have use Gatling **Official Response from Diego Salinas:** > Thank you for the thoughtful review, and especially for calling out our CI/CD integrations with Jenkins, GitLab, and GitHub Actions. Helping teams catch performance regressions before they hit production, especially ahead of high-stakes events like Black Friday, is exactly what we're aiming for. We also appreciate the feedback on the learning curve for non-developers. Since you last reviewed us, we've made this a priority. We launched a Recorder that lets you generate Gatling scripts from recorded actions rather than writing the Scala code by hand, plus AI-powered migration tools to help teams move existing JMeter and LoadRunner test suites into Gatling. We've also rolled out AI-powered documentation to make it easier to get unstuck without needing deep Scala expertise. Together, these are meant to lower exactly the barrier you described. We'd love for you to try them out and let us know how they compare to your experience so far. Thanks again for using Gatling and for the detailed feedback. ### 37. Massive scale, great customization, great customer support **Rating:** 4.0/5.0 stars **Reviewed by:** Syed Ahmed A. | Chief Software Architect / Senior Software Engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** July 04, 2023 **What do you like best about Gatling?** The customer support has been some of the best I have come across. We required complex use cases for requests and gatling's DSL supported all the customizations we needed. Being able to scale and test load test at massive traffic (the main reason we opted for gatling - we wanted to test at 1 million requests per second from multiple regions) has been amazing **What do you dislike about Gatling?** The public API for automating your scenarios rather limiting. i.e you can run simulations but not create them. Perhaps that has changed now Although now it supports Java, when we started they only supported Scala. **What problems is Gatling solving and how is that benefiting you?** We needed to test at a massive scale, generating traffic of 1 million requests per second which was coming in from multiple regions. Gatling integrated easily with AWS and allowed us to test our application. As a developer it provided a lot of flexibility to generate complex traffic scenarios, and the UI looked good enough to be presented to managers. ### 38. Market leader in the world of performance testing **Rating:** 5.0/5.0 stars **Reviewed by:** Eugene A. | I break stuff for a living, Mid-Market (51-1000 emp.) **Reviewed Date:** July 30, 2023 **What do you like best about Gatling?** - 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 - Cloud managed solution is also available **What do you dislike about Gatling?** There is nothing I *dislike* about Gatling, I really have just one point here: - Gatling is relatively new so community is smaller than of peers (if you have to write non-trivial solutions, you are likely to be the first to do it) **What problems is Gatling solving and how is that benefiting you?** Gatling is a great solution for load testing due to its extensibility, performance and out of the box reporting. It is easy to compose and run the load suite in a matter of hours, even when you have no previous experience. Gatling repeatedly allowed me to identify weak chains in the complex application environment and address them. ### 39. One of the best open source tool for load testing **Rating:** 3.5/5.0 stars **Reviewed by:** MANIKANDAN B. | IT Specialist, Enterprise (> 1000 emp.) **Reviewed Date:** September 28, 2023 **What do you like best about Gatling?** # The flexibility with coding language # Gatling academy is super useful # JMS support is super useful which many open source testing tools lack # Documentation is super clear and useful # The integration options available are good **What do you dislike about Gatling?** Working with complex payload are tricky as it lacks some standard functions to modify the response. Also apart from official documentation, issues in Java based Gatling is not easy to avail **What problems is Gatling solving and how is that benefiting you?** Open source and good features **Official Response from Diego Salinas:** > We're glad to hear that you find Gatling to be one of the best open source tools for load testing. We appreciate your feedback on the flexibility with coding language, the usefulness of Gatling academy, JMS support, clear documentation, and integration options. We understand your concerns about working with complex payloads and the availability of support for Java-based Gatling. We will take your feedback into consideration for future improvements. Diego from Gatling ### 40. Extremely versatile and powerful performance testing tool **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Broadcast Media | Enterprise (> 1000 emp.) **Reviewed Date:** July 20, 2023 **What do you like best about Gatling?** 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. **What do you dislike about Gatling?** 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. **What problems is Gatling solving and how is that benefiting you?** 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. ### 41. Fantastic tool that gets the job done **Rating:** 4.5/5.0 stars **Reviewed by:** Joseph P. | Small-Business (50 or fewer emp.) **Reviewed Date:** August 17, 2023 **What do you like best about Gatling?** 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. **What do you dislike about Gatling?** 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. **What problems is Gatling solving and how is that benefiting you?** 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. ### 42. Robust Load Testing tool **Rating:** 4.5/5.0 stars **Reviewed by:** Bhawna R. | Software QA Analyst, Small-Business (50 or fewer emp.) **Reviewed Date:** June 27, 2023 **What do you like best about Gatling?** It is a robust load-testing tool out in the market. It doesn't load your computer much when testing with 1000s of virtual users. Because of the scripting-based tool, it is easy to tweak and try out different options. It supports multi-languages - Scala, Java and Kotlin. It also provides the ability to perform load testing for websocket based applications. I love the beautiful reports. **What do you dislike about Gatling?** Because of no UI, there is a little of bit steep learning curve for non-programmers which could be frustrating. Documentation could be more precise like currently, for maven projects, documentation says for Java 8 use this dependency, but for Java 11 use another dependancy. I wasn't sure if it supports a higher version of Java because I had Java 19 installed and was getting some errors. I thought it could be due to an unsupported Java version. Later got to know it supports all versions. **What problems is Gatling solving and how is that benefiting you?** I wanted to test a feature implemented using WebSocket, and Gatling had the ability. Also reports are beautiful, easy to read and understand. I was able to tweak the testing scenarios easily. Didn't need to re-record . ### 43. Gatling Performance Test Tool **Rating:** 3.0/5.0 stars **Reviewed by:** Juan C. | Head of Quality & Scalability, Mid-Market (51-1000 emp.) **Reviewed Date:** December 20, 2023 **What do you like best about Gatling?** The data points in the report are very easy to digest. **What do you dislike about Gatling?** Lack of updates in the tool that generates the files **What problems is Gatling solving and how is that benefiting you?** Performance testing ### 44. Powerful but involved. Easier than Java **Rating:** 1.5/5.0 stars **Reviewed by:** Alan J. | Small-Business (50 or fewer emp.) **Reviewed Date:** June 28, 2023 **What do you like best about Gatling?** Lots of tools to express the testing scenario needed. You can automate many steps and have them graphed nicely in an understandable way at the end of the run. After parametrized, same scenario can be run ove multiple targets for comparison. **What do you dislike about Gatling?** Too steep learning curve, and very opinated about how to write the tests. Stuff needs to be idempotent or pure-functions, so some branch decisions are very hard to do. That until they removed some feature I used. Now it is impossible to do some decisions. **What problems is Gatling solving and how is that benefiting you?** I have a target load that is hard to produce manually, and a expected flow of many steps. Gatling graphs help perceive where are the bottlenecks. Also keeps the test reproductiple within the many developers ### 45. Great performance tests as a code experience **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Computer Software | Enterprise (> 1000 emp.) **Reviewed Date:** September 23, 2023 **What do you like best about Gatling?** 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. **What do you dislike about Gatling?** Java version compared to Scala lacked some small features when it comes to some advanced usage. One also has to get used to specific ways of dealing with immutable session objects which sometimes can be tricky. **What problems is Gatling solving and how is that benefiting you?** Genereates load that I can esily shape both in terms of functional coverage and load profile **Official Response from Diego Salinas:** > Hi, thank you for this review! Really glad to hear the DSL and CI/CD integration made it easy to bring good coding practices and IDE support into your performance testing setup. That's a big part of why we built it as code in the first place. Since this review was written back in 2023, one thing worth flagging: the Java DSL has closed a lot of the gap with Scala since then, so some of the advanced-usage friction you ran into may no longer apply. Worth a look if you're still using the Java version. Thanks again for taking the time to share your experience. Diego from Gatling ### 46. Kubernetes Scalability & application performance testing **Rating:** 4.5/5.0 stars **Reviewed by:** Andrii S. | Automation and Test Architect, Mid-Market (51-1000 emp.) **Reviewed Date:** September 12, 2023 **What do you like best about Gatling?** 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. **What do you dislike about Gatling?** No native integrations with monitoring tools (DataDog. etc). No test scehduler. **What problems is Gatling solving and how is that benefiting you?** Release-to-Release API perfromance tests for web-faced application. Kubernetes scalability & Chaos testing were Gatling acting as a traffic load provider with defineded test acceptance criteria (as a code). **Official Response from Diego Salinas:** > Hi Andrii, thank you for this review! Glad to hear the Maven integration, GitHub Actions support, and Gatling Enterprise's graphs and support experience have been working well for your Kubernetes scalability and release-to-release performance testing. That's a great use case, especially combining load generation with defined acceptance criteria as code. Wanted to flag two updates since you wrote this in 2023: we now have native integrations with Datadog, Dynatrace, InfluxDB, and OpenTelemetry, so the monitoring gap you mentioned should be closed. Thanks again for the detailed feedback, and for being a long-time Gatling user. Diego from Gatling ### 47. Gatling cloud is a great tool for load testing **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Legal Services | Mid-Market (51-1000 emp.) **Reviewed Date:** April 29, 2023 **What do you like best about Gatling?** Gatling is a great tool for load testing, it is easy to get on with, it could handle our specific test requirements easily. Produced tests reporting were clear enough, and made it possible to pinpoint required actions on our app. We did not encounter any issue using the cloud version! **What do you dislike about Gatling?** It is quite specific to our business requirements, but it's not (yet?) possible to skip already used lines in data CSV files. As well, some report graphs in the cloud version cannot be enlarged. **What problems is Gatling solving and how is that benefiting you?** We have some customer requirements about the number of users that our app can handle. Gatling helps us check these theresold, and pinpoint HTTP requests that takes too much time and need correction or rework. ### 48. Performance Tester **Rating:** 4.0/5.0 stars **Reviewed by:** krishna Moorthy L. | Small-Business (50 or fewer emp.) **Reviewed Date:** September 21, 2023 **What do you like best about Gatling?** Lightweight tool can simulate larger Number of virtual users from single load generators machine It's reduce cost for investment in hardware components **What do you dislike about Gatling?** Need detail load test report like response time breakdown graphs for component based.Runtime load test feeds. **What problems is Gatling solving and how is that benefiting you?** Can simulate large volume of load test from single load generator **Official Response from Diego Salinas:** > We're glad to hear that you find Gatling to be a lightweight tool that can simulate a large number of virtual users from a single load generator machine, reducing hardware investment costs. Thanks for using our platform. Diego from Gatlin ### 49. How gatling help us with perfomance testing **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Computer Software | Mid-Market (51-1000 emp.) **Reviewed Date:** June 09, 2023 **What do you like best about Gatling?** It's very easy to use. We have built a complete work environment. We have built different scenarios that we play on our software. We can adjust the number of workers, and the developers allow us to work on issues encountered during testing. Gatling improves the quality of our software by avoiding performance issues. Gatling has become indispensable. **What do you dislike about Gatling?** The language used was Scala (but now it is possible to work in java). It was another language to learn and support in our comapny. The documentation sometimes is quite simple, it will be helpful with complex samples. **What problems is Gatling solving and how is that benefiting you?** Hundreds of people can use our software simultaneously, using different scenarios, and response times must be constant. Gatling helps us achieve this goal. The benefits are immediate, this leads to customer satisfaction because we solve complex incidents before going into production. ### 50. Gatling API Performance Testing Tool **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Public Relations and Communications | Small-Business (50 or fewer emp.) **Reviewed Date:** June 16, 2023 **What do you like best about Gatling?** Gatling gives a scripting platform narrowing down the gap between developer and tester. It also helps in shift-left and easy integration in CI-CD pipeline achieving frequent deployment. **What do you dislike about Gatling?** Gatling being a new tool in the market and an emerging one trying to deliver the most by supporting http, JDBC and MQTT Protocol in three different languages still is not comparable with other tools such as LR or JMeter. **What problems is Gatling solving and how is that benefiting you?** We are using Gatling for testing our api in different environments with different userload and scopes. We use Gatling for API testing along with Performance testing. ## Gatling Discussions - [Is Gatling better than JMeter?](https://www.g2.com/discussions/is-gatling-better-than-jmeter) - 1 comment, 3 upvotes - [What are the protocols supported by Gatling?](https://www.g2.com/discussions/what-are-the-protocols-supported-by-gatling) - 1 comment - [View Gatling pricing details and edition comparison](https://www.g2.com/products/gatling/reviews?section=pricing&secure%5Bexpires_at%5D=2026-08-08+14%3A54%3A12+-0500&secure%5Bsession_id%5D=e9d11cde-d0ef-4ba9-9d6d-b9c926b8d7b4&secure%5Btoken%5D=70f76c248dc08fdb3e23feac449913f6c82e79e55b79e942901161ac1dcb55c8&format=llm_user) ## Gatling Integrations - [Apache Kafka](https://www.g2.com/products/apache-kafka/reviews) - [AWS CloudFormation](https://www.g2.com/products/aws-aws-cloudformation/reviews) - [AWS CloudFormation](https://www.g2.com/products/aws-cloudformation/reviews) - [AWS CodeBuild](https://www.g2.com/products/aws-codebuild/reviews) - [AWS Secrets Manager](https://www.g2.com/products/aws-secrets-manager/reviews) - [Azure DevOps Server](https://www.g2.com/products/azure-devops-server/reviews) - [Bamboo](https://www.g2.com/products/bamboo-metrix-bamboo/reviews) - [Bamboo](https://www.g2.com/products/bamboo/reviews) - [Bamboo](https://www.g2.com/products/bamboo-bamboo/reviews) - [Buildkite](https://www.g2.com/products/buildkite/reviews) - [Buildkite](https://www.g2.com/products/buildkite-buildkite/reviews) - [CircleCI](https://www.g2.com/products/circleci/reviews) - [Claude Code](https://www.g2.com/products/anthropic-claude-code/reviews) - [Concourse CI](https://www.g2.com/products/concourse-ci/reviews) - [Cursor](https://www.g2.com/products/cursor/reviews) - [Datadog](https://www.g2.com/products/datadog-datadog/reviews) - [Datadog](https://www.g2.com/products/datadog/reviews) - [Dynatrace](https://www.g2.com/products/dynatrace/reviews) - [GitHub](https://www.g2.com/products/github/reviews) - [GitLab](https://www.g2.com/products/gitlab/reviews) - [Google Cloud Build](https://www.g2.com/products/google-cloud-build/reviews) - [Helm](https://www.g2.com/products/helm-2026-06-08/reviews) - [HELM](https://www.g2.com/products/helm/reviews) - [Helm](https://www.g2.com/products/helm-helm/reviews) - [Helm](https://www.g2.com/products/helm-2026-05-29/reviews) - [InfluxDB](https://www.g2.com/products/influxdata-influxdb/reviews) - [Jenkins](https://www.g2.com/products/jenkins/reviews) - [Jira](https://www.g2.com/products/jira/reviews) - [Karate Labs](https://www.g2.com/products/karate-labs-2023-05-24/reviews) - [Maven](https://www.g2.com/products/mavenresearch/reviews) - [Maven](https://www.g2.com/products/maven-2025-11-28/reviews) - [Maven](https://www.g2.com/products/maven-maven/reviews) - [Microsoft Teams](https://www.g2.com/products/epc-group-microsoft-partner-microsoft-teams/reviews) - [Microsoft Teams](https://www.g2.com/products/microsoft-teams/reviews) - [New Relic](https://www.g2.com/products/new-relic/reviews) - [New Relic](https://www.g2.com/products/new-relic-new-relic/reviews) - [npm](https://www.g2.com/products/npm/reviews) - [OpenJDK 8 (Java 8) on Ubuntu 18](https://www.g2.com/products/openjdk-8-java-8-on-ubuntu-18/reviews) - [OpenTelemetry](https://www.g2.com/products/opentelemetry/reviews) - [Postman](https://www.g2.com/products/postman/reviews) - [Prometheus](https://www.g2.com/products/prometheus/reviews) - [sbt](https://www.g2.com/products/sbt/reviews) - [Slack](https://www.g2.com/products/slack/reviews) - [TeamCity](https://www.g2.com/products/teamcity/reviews) - [TestMu AI](https://www.g2.com/products/testmu-ai/reviews) - [WindSurf AI IDE](https://www.g2.com/products/windsurf-ai-ide/reviews) ## Gatling Features **Functionality** - Stress Testing - Extreme Cases - Test Variety - Web Testing - Regression Testing - Mobile Testing - Cloud Load Testing - UI Testing - Cross Browser Testing - Parallel Testing - Performance Testing **Agentic AI - Software Testing** - Autonomous Task Execution - Natural Language Interaction - Proactive Assistance **Reporting** - Reporting - Uptime Reporting - Web Traffic Reporting - Real-Time Reporting **Additional Functionality** - API - Third-Party Integrations - Secure Data Storage - Configuration Management - Trend Analysis - Real-Time Monitoring - Reporting/Analytics - Forecasting - Data Extraction - Real-Time Analytics - Reporting & Statistics - Engagement Tracking - Data Synchronization - Activity Tracking - Productivity Analysis - Browser Performance Metrics - User Management - Real-Time Data - Data Transformation - Performance Management - Data Import/Export - Server Monitoring - Bottleneck Identification - Alerts/Notifications - AI Copilot - Performance Metrics - Visual Analytics - Activity Dashboard - Status Tracking - Monitoring - Charting - Data Storage Management - Testing Management - Software Testing Management - Remote Monitoring & Management - Testing Scripts - Generative AI - Rules-Based Workflow - Assessment Management - Scheduling - Drag & Drop - Data Visualization - Website Analytics - Load Scenarios - Multiple Data Sources - Benchmarking - Debugging - Predictive Analytics - Bug Tracking - Test Performance Metrics - Issue Tracking - Desktop/Application Virtualization - Issue Management - Continuous Integration ## Top Gatling Alternatives - [Apache JMeter](https://www.g2.com/products/apache-jmeter/reviews) - 4.3/5.0 (152 reviews) - [k6](https://www.g2.com/products/k6/reviews) - 4.8/5.0 (31 reviews) - [Postman](https://www.g2.com/products/postman/reviews) - 4.6/5.0 (1,755 reviews)