Apache JMeter Reviews

This is a cost-effective tool, which provides people the ability to do POCs without worrying about costs.

Apache JMeter provided us with the opportunity to test applications for clients who did not have the budget to employ heavy-duty tools like LoadRunner.

Additionally, due to ease of installation, it can be installed in any client network, without the requirement for port opening.

API testing, Database Testing, and MQ testing can be done with ease.

The tool should be made a bit more robust, and better support should be made available.

I set a script reporting and execute test report and analysis on almost all stages of the performance cycle except in regards to requirements and the environment.

we saved a lot on licenses for commercial tool

The features that helpful are the coding and the opportunity to work with the SQL directly in order to report on the data. You can collect all the test data from DB with these and then do post test execution metrics collection as well(if you need DB)

RegEx Extractor needs improvement. It's a headache for many people. The solution could use some sort of educational features to offer tips and hints to help users navigate it better. They should improve the manuals and help files. I've searched the internet for answers over the past year or so, and I haven't come across anything that is helpful. The community help files are pretty good, but their own help files are not.

In the next release, it would be helpful to offer more flexible graph handling to be able to combine different metrics into one graph.

quitre stable but keep an eye on RAM consumption and smart execution tips (can see on their site)

Scalability is good, though you need to be aware of distributed and non guis test execution modes. 

It's a free tool, so they don't offer technical support. If you need help, you need to Google and search for answers on your own.

I've used LoadRunner in the past, among other solutions. I switched to Apache because it is free. Other tools are much too expensive and can cost up to $50,000 a year if you are looking at commercial options.

Now Neoload probably the best one (better than Load runner as per my subjective perception) but it's a way too costly 

please take a look at ROI and scal of performance tests. For big projects and organizations consider Load Runner or Neoload, but if you have small project, most likely you wil lstop on Apache Jmeter. Also it depends on the protocol support. But because of big community, Apache jmeter has constant income of new plugins developed

For people thinking about implementing the solution, I would advise that they know what protocols they want to work with. I would recommend doing an evaluation of script maintenance. You need to see how stable your automation disk and performance is. 

I would rate this solution nine out of ten. The solution offers a lot of plug-ins and a huge, continuously developing community that is regularly offering new features and plug-ins.

We primarily use the solution for performance download testing.

It's a solution that's easy to use. It's a bit different from SoapUI and LoadUI.

The user interface is a little bit tricky.

The solution is very stable.

It's not 100% scalable like LoadUI, but LoadUI is very expensive. We're an outsourcing company, so we have approximately ten users. We may have plans to expand in the future.

The solution doesn't have technical support. If we need answers, we look for them on the internet.

Previously, we used the basic version of LoadUI. We switched because LoadUI is very expensive and Apache JMeter is free.

The initial setup was complex. We did have it done in a day. It took approximately one hour. We have about five to six people that manage the solution.

The solution is free. You don't need to worry about licensing costs.

We didn't evaluate other options before choosing this solution.

We are using the private cloud version of the solution.

I would rate this solution eight out of ten. If it had a bit of a better user interface, I would rate it higher.

Extremely light weight.

Very easy to download and setup the entire infrastructure (Controller +LGs)

Ease of scripting

Host of plugins which further boost its effectiveness

Availability Non-GUI mode which consumes even lesser resources than already lightweight GUI version.

Robust scripts which could handle build changes

Easy LG(Master & Slaves) configuration setup

Very lightweight and low usage of resources 

GUI tends to freeze and shutdown under more load

Ctrl+z( Undo doesn't work) so gets very inconvenient at times

Cannot do a mass replace( Ctrl+H) on the GUI ( can do it if script is opened via notepad++)

Re-iteration problems during errors - Usually we have login in once only controller, Action in Loop controller and logout in once only controller. Now if an error comes when the user simply logouts due to some unhandled error then the script expects that your session would continue but if that error has made you logout then your next iterations won't go through and vice versa. Suppose you put everything in loop controller and error doesn't log you out then the script start to login when you are already logged in and tends to fail.

We've had no issues with deployment.

See above Room for Improvement.

We've had no issues with scalability.

Almost all features provided by JMeter are helpful.

We have a solution called Service Quality Manager portal and is a web based solution to do service management. We do performance testing of this solution using JMeter. It allows us to simulate a load of concurrent users on our application and find out performance bottlenecks in the application.

Reporting feature can be improved to provide better test results.

We have been using JMeter for 5 years.

I did not encounter any issue while deploying JMeter.

I did not encounter any issue with stability.

Yes, While running with a large number of simulated users, sometimes we got thread exceptions and we restarted our testing simulation.

As such there is no customer service provided by Apache for JMeter. This software is free to use under Apache licensing system.

We tried BadBoy but it lacked features.

Initial setup of JMeter is simple. A user can go ahead and start using it just by following it's documentation.

We implemented JMeter using our own in-house team.

I am not sure yet.

As it is java based software an can run on any platform supporting JVM.

I would suggest to verify one's own business need and evaluate certain parameters first like Feasibility and Reliability of Automation, Ease in maintenance of automated test cases, Time saving in Manual or Automated Testing.

• Recording/Playback
• Templates for test plans (NEW)
• Integrate with Java and many other scripting languages
• Integrating with external plug-ins

• The recording feature makes it easy to create test plans
• They have templates that make starting very easy (this feature is added recently)
• Supports a lot of protocols (HTTP, HTTPS, FTP , SMTP etc)
• Simplicity of use
• As compared to commercial tools, it provides better reporting features through third-party plug-ins
• There's also a huge community around tool, and because of that when there's an issue, you can get solutions easily, and without cost For example, we dis a very complex testing of HL7 protocols, which JMeter doesn't support directly, but it's extendable to support the protocols
• Supports Java and other scripting languages and can extend capabilities.

Reporting could be better if it could be like commercial tools. For example, a nice chart and visualizations. You can’t rely on the first 100 test results because the ramp-up and ramp-down time gives false results with outliers. It would be great if an option to ignore first 100 and last 100 records from results and then generate reports, should be great. Needs to support more concurrent users by single JMeter instance (agent/slave)

I've been using it for over last five years, and it is a major, active open source tool.

No issues with recent releases

There are issues when tests are stopped with large number of concurrent users. Test is not stopped as expected.

There is a huge community around JMeter. Hence free support is available to the users.

Excellent (from the community)

Grinder. Grinder was not user friendly and had to do lot of coding and low level configurations. It was lighter than JMeter.

Initial setup is straight forward. You need to have have JDK or JRE for running JMeter.

We have a team of testers capable of managing the JMeter perfromance testing project effectively.

It's easy to use and free, a huge community, and it offers a risk free to start, so use it for application performance testing. It supports connectivies with databases, FTP, and other system protocols.

I like the ease of using JMeter. It can be downloaded and can be used to record and run load tests. JMeter can record, run and create reports easily without the need to have licenses, complex installations and paid support. It can be used to performance test services, web applications, database queries, LDAP, etc.

We use JMeter for performance testing. We are able to know which module is lagging behind in performance, whether the software or hardware upgrades have improved the performance or not.

I think JMeter hangs up on large loads. I have seen JMeter becoming unresponsive in the middle of a test. It is because of garbage collection in JMeter. We use best practices to mute all listeners, use non GUI mode, etc., but even with many best practices JMeter pauses in between load tests.

It is a open source tool.

My advice would be to have load generator machines. Do not run JMeter (or any load testing tool) from a desktop. Do not have just one JMeter installation to generate load. Use several JMeter instances to distribute load. If possible, use JMeter in Client Server mode.