Apache JMeter Reviews

We are using it for load testing. We test other companies' programs.

We are using it just for load testing. We are using its free version, and it is scalable.

I am not satisfied with this solution. Its UI side is not so easy to use for beginners. It should be easier. 

Modeling a test is difficult. If you don't have much knowledge, you won't be able to do it easily. Testing APIs is also difficult.

For JSON, you can use tools such as JSONBuddy, but they are difficult to get in JMeter. It should be easy to get JSONBuddy from the website. I have to use BlazeMeter only to get JSONBuddy.

It has been about five months.

It is not so stable.

It is scalable.

Their support is fine. There are not many Apache documents, but you can find other documents on the web.

It is not so difficult.

We are using the free version.

I would rate it a seven out of 10.

In general, the primary use case of this solution is for performance testing and load testing.

Typically it is for load tests. They have to focus on three metrics including throughput, response times, and the utilization of the resources including the CPUs.

We are delivering some bank houses with performance tests, through JMeter.

The deployment model varies depending on the client. Some have a private line.

From the customers' perspective, the most valuable feature is the price.

The most valuable feature for us is the available information on the forums and to be able to discuss and get answers from the people that are involved in using this tool.

They have to find a way to prepare the script or to prepare a detailed analysis. We have to collect all the information on each of the services we have to call. Based on this they have to collect in the phase of preparation for the performance test and then we can run our audit. It is easy to prepare a script to run a performance test.

You can't rely on the support. It's something that is not fully working.

The scalability of this solution needs some improvement.

There is some work to be done with the integration.

This solution is stable, but it does have one limitation with the number of throughputs. For example, if I want to generate four, five, or two thousand people working concurrently then they have to prepare our setup for ten PC servers.

Normally they can run a load for five thousand people, customers, or users working concurrently. It is scalable but needs some improvement.

The technical support on the site is not fully functioning.

The initial setup is easy and straightforward.

You can have it running within thirty minutes.

I had always implemented this solution myself, but It's been a couple of years since I did it last.

Now it is done through our company technicians.  I just coordinate activity-performance tests for our customers.

This is an open-source solution, and there are no fees.

The requirements for most of our customers is to provide them with cheap solutions, and most prefer not to pay for software. This is the right solution for them based on some of the open-source tools that are available.

There are some commercial solutions that provide better integration to the solutions that must be tested when running loads.

I would rate this solution an eight out ten.

I mainly use JMeter to check network capacity.

JMeter's most valuable feature is the RegEx Extractor.

Running JMeter in GUI mode uses a lot of memory, which means we need to switch to a non-GUI mode when using a heavy load. There's also a steep learning curve for how to use regular expressions.

I've been using JMeter for over three months.

I would rate JMeter's stability seven out of ten.

I would rate JMeter's scalability as six out of ten.

The initial setup was very easy and took around five minutes.

I implemented JMeter myself.

JMeter is open source and available free of charge.

I would recommend JMeter to other users as it's easy to use and open source, and overall, I'd rate it eight out of ten.

I implement this solution for my clients.

It is very quick and user-friendly.

If the solution was GUI based, I believe that it would be more versatile.

I have been using this solution anywhere from six to eight years.

The solution is stable, I would definitely recommend it to those who are considering it.

The solution is scalable.

No licensing is required as it is a free, open-source tool.

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.

Our primary use case for the solution is performance testing for applications, and we deploy it on the cloud and on-premises.

We find the load testing feature valuable.

The reporting section of the solution can be better. Additionally, more plugins can be included in the next release.

We have been using the solution for approximately 15 years and are currently using version 5.3.

The solution is stable.

The solution is scalable, but it all depends on the application. However, it is usually scalable by up to 2500 users. However, if you want to use it for any number of users, you can use JMeter as long as your machine supports it.

We do not have experience with customer service and support because everything is stable.

We previously used LoadRunner.

The initial setup is straightforward. I rate it a nine out of ten.

The tool is open source, so we do not pay for licensing.

I rate the solution a nine out of ten. I advise new users to enhance their understanding of the solution via Youtube.

We use it to measure the performance of the system and for balancing.

We like that Apache JMeter has different features and different plugins and that they are free of charge.

We also like that lots of people use it. So, if we happen to get stuck at some point, then we can search for solutions on Google and find them.

Report generation needs to be improved. It is quite difficult to get to.

We've been using Apache JMeter for two years.

It is quite stable.

It is a scalable solution.

On a scale from one to ten, I would rate Apache JMeter at nine. I would recommend it for medium-sized businesses.

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.