G2

Sree K.

Software Development Engineer in Test III

Computer Software

Mid-Market (51-1000 emp.)

7/27/2026

"Flexible, Reliable Performance Testing with Detailed Metrics and CI/CD Integration"

5/5

What do you like best about Apache JMeter?

What I like most about Apache JMeter is its flexibility across different types of performance testing. I mainly use it for API performance testing, load testing, stress testing, and other non-functional testing, and it has been reliable in all of these scenarios. Building test plans, configuring thread groups, parameterizing test data, and validating responses are all fairly straightforward once you get familiar with the tool.

Another major advantage is the level of detail in the reports and metrics it provides. Response times, throughput, error rates, and other performance statistics make it much easier to spot bottlenecks and understand how an application behaves under different load levels. This has helped us catch performance issues early, before they make it to production.

I also appreciate that it integrates well with CI/CD pipelines, so performance tests can be included as part of our release process. Because it’s open source, there’s no licensing cost, and the large community makes it easy to find plugins, documentation, and solutions when needed.

Overall, Apache JMeter has become an important part of my testing workflow. It helps me validate application performance with confidence, while saving time through automation and repeatable test execution. Review collected by and hosted on G2.com.

What do you dislike about Apache JMeter?

One area where Apache JMeter could improve is the user interface. While it’s functional, it can feel a bit dated compared to many modern testing tools, and new users may need some time to get comfortable creating, organizing, and maintaining complex test plans.

Another limitation is that running very large load tests directly from the JMeter GUI can consume a significant amount of system resources. For larger performance tests, it’s usually better to execute tests in non-GUI mode or use distributed execution, but that adds some extra setup and configuration.

Debugging complex test scripts can also be time-consuming, especially when multiple parameterized requests, correlations, and assertions are involved. These aren’t major issues, but they do contribute to a learning curve for beginners.

That said, once you’re familiar with the tool and follow best practices, it remains a dependable choice for performance and API testing. Review collected by and hosted on G2.com.

What problems is Apache JMeter solving and how is that benefiting you?

Apache JMeter helps us identify performance issues before an application is released. I use it for API performance testing, load testing, stress testing, and other non-functional testing to understand how the application behaves under different levels of user traffic. Rather than discovering performance bottlenecks in production, we can detect slow APIs, response-time degradation, memory issues, and system limits much earlier.

It also helps us validate whether new releases meet expected performance requirements. By comparing test results across builds, we can quickly see if a change has negatively affected performance and address it before deployment.

The biggest benefit is increased confidence during releases. We can simulate real-world load, measure key performance metrics, and share detailed reports with the team to support release decisions. This has helped reduce performance-related issues in production and ensures users have a more stable, responsive experience. Review collected by and hosted on G2.com.