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.

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.

It mimics a crowd of users hitting your app at the same time, which is how you actually catch the bottlenecks. Need more load than one machine can generate? Spread the test across several. While it runs, it tracks response times, throughput, and error rates, then charts all of it so you're not reading raw numbers. Review collected by and hosted on G2.com.

Expect a steep learning curve. Basic tests are fine, but once you get into anything advanced you'll need real scripting chops. And the GUI is a resource hog: run a big test through it and things slow to a crawl or just fall over. You're better off running headless or spreading it across machines. Review collected by and hosted on G2.com.

Helpful for load testing. I like various numbers of listeners to show the results data. Easy to use for performance testing. Review collected by and hosted on G2.com.

Sometimes performance of the application goes down during testing. It becomes complex to write the script in Jmeter for load testing when there is several data. Review collected by and hosted on G2.com.

Apache JMeter is a great tool to test out new APIs and do continuous load testing on the same. It helps understand latency figures and effectively gives metrics for P95, p50, etc. Review collected by and hosted on G2.com.

It is very complicated to use and you need to have technical know-how for the same. There is no use case guide for handholding as well. Review collected by and hosted on G2.com.

Easy to perform performance testing using JMeter.

I can easily perform load testing by increasing number of threads on any application. Review collected by and hosted on G2.com.

I face a slight hang issue when doing performance testing. Review collected by and hosted on G2.com.

Once you have the basic knowledge about JMeter you will be able to create customized routines to test your code, it could be web pages, API or complex scenarios where the final user needs to follow a specific path, the tool is very useful to stress systems and simulate overload of users Review collected by and hosted on G2.com.

as a beginner user you will need to spend some time to rump up and start to use the tool ins your testing, but you can find a lot of kind of tutorials on the internet and youtube, even if you prefer paid, you have the option to acquire training on Udemy Review collected by and hosted on G2.com.

Best tool for performance stress and load testing Review collected by and hosted on G2.com.

Something it gets slow and start lagging Review collected by and hosted on G2.com.

It is an open source Java platform build tool to automate performance testing scripts. Mostly used for Non-Functional testing. It has ease of use in the UI. Implementation or installation is quite easy. Review collected by and hosted on G2.com.

Some of the integrations are not yet implemented and less documentation is available to integrate tools. Plugin updates are very minimal. Customer support is a major issue since it's an open source tool. Review collected by and hosted on G2.com.

JMeter is appreciated for its robustness and versatility in load testing and performance measurement of web applications, APIs, and various protocols. It has a good feature that allows us to download all metrics. Review collected by and hosted on G2.com.

I wouldn't say I dislike it, but a common criticism of JMeter is that its user interface can be overwhelming and less intuitive for new users, and it lacks built-in reporting and visualization tools. Review collected by and hosted on G2.com.

JMeter is a great application for Load testing.

The best thing about JMeter is that you can keep concurrent loads and you can run a large amount of threads to really test your application or server's capacity. Review collected by and hosted on G2.com.

The thing that I dislike about JMeter is that it can get quite complicated for a person to use, although it has a UI but still you have to depend on the CLI mode for running larger amount of threads. Review collected by and hosted on G2.com.