Apache JMeter Reviews

I am using the solution for load, endurance, and performance testing.

Scripting with the solution is good.

The solution needs to improve reporting. Currently, there is not enough automation involved with the feature. For example, there should be an automatic way of saving reports. I have also found the recording should be improved too. When you are entering a launch in the controller the recording request should be inside it. Lastly, if they could make the technology better in terms of speed, this would help us.

I have been using the solution for two months.

When I compared this solution to others there were variations in the response times but it is stable.

We have used the current solution process for approximately 400 users.

The customer service is quite good. They get a lot of people requesting support but even under those conditions, they are still efficient at responding.

I have previously used NeoLoad.

The setup is easy, it is not that complex.

I would recommend Apache Jmeter. 

I rate Apache JMeter an eight out of ten.

On-premises

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.

1. GUI is very user friendly 2. It's a pure Java tool, which enables me to run it on any platform (i.e. platform independent) 3. Free tool & easy to get.

1. It does not support recording SSL 2. Supports only web based applications 3. Cannot change the recorded scripts

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.