Apache JMeter Reviews

We use this solution mostly for creating scripts, load testing, and performance testing. If my client doesn't have a tool or I don't have a tool, I try to leverage JMeter because it's an open-source tool.

I personally use JMeter for things which cannot be covered by our load testing tool, which is OATS, Oracle Application Testing Suite. This is a tool that was developed by Oracle but is no longer in use because Oracle has stopped developing it.

The solution is deployed on-prem and on private and public clouds.

JMeter should be more stable. Every time there is a new release coming up, a lot of its older functionalities or the new functionalities that are brought in are not very well-documented. It should be documented properly, and there should be proper use cases. A lot of the newer features don't work, and sometimes you have to spend a lot of time maintaining the scripts. That is something JMeter could probably look at.

For example, in JMeter 5 they brought in a lot of new controllers. But there isn't a lot of documentation available on the Apache site on how you're supposed to use those controllers. They've explained the controller functionality, but there aren't any proper use cases to show that. 

I have been using JMeter for a long time and do a lot of work with this solution.

It's not stable. With every new release, they come up with newer features, which aren't always very stable. So, stability is a concern.

It is scalable. You can scale up to 1,000 users in JMeter. If you can put up four slave servers, you can easily ramp up to 1,000 users. That's not a problem.

Because it's open-source, a lot of organizations try to leverage JMeter into everything. I don't think JMeter is currently very adaptable to all the technologies. That is something Apache should think of – incorporating other technologies and other tech stacks, which can be scripted from JMeter and tested using JMeter.

On a scale of 1 to 5, I would rate technical support 2.5

They're not very good because JMeter is an open-source tool. You can raise a bug to JMeter, and they might fix it or they might say that, "We will actually fix this in the next release." So, because it's an open-source tool, you do not get dedicated support. You have to raise tickets and wait. If you use BlazeMeter, the support is probably a little better because you can take your issues there.

I don't think support is great if you compare it with tools like NeoLoad or LoadRunner where they have a dedicated support team. You can raise tickets. You have a direct conversation with their engineers. They can help you understand where the issue is exactly. That kind of support is not in JMeter, at least not now. BlazeMeter has it, but I have not used BlazeMeter support, so I'm not sure how it is. But from what I have seen with JMeter, support is not great.

It is straightforward, but for JMeter 5, since they have introduced SSL handshake at the slave level, that becomes a little bit of a challenge for somebody who is doing it for the first time if you're doing a distributed execution, that becomes a challenge.

But since there was not enough documentation, I had to do a lot of troubleshooting on my own, since it was new. Now there's a lot of documentation available, but initially, there was not much documentation.

JMeter is pretty easy to use if you are using it for the purpose of only developing scripts. You can just uninstall the file and you can start using it. The only challenge happens if you're trying to access the internet over any kind of proxy. Then, you'll have to start it via the proxy mode.

Otherwise, deploying JMeter is pretty easy compared to other tools. You just have to download, unzip, and you are ready to go.

We installed JMeter ourselves.

I would rate this solution 7 out of 10.

We use Apache JMeter for load testing, where we provide the throughput time. Apache JMeter allows me to give any number of users to put the load in a particular time frame. With Apache JMeter, we won't need multiple tools with the application or to give a load for the application.

Apache JMeter's UI can be made more colorful.

I have been using Apache JMeter for two years.

I rate Apache JMeter ten out of ten for stability.

Around 10 people are using the solution in my team.

I rate Apache JMeter a nine out of ten for scalability.

Apache JMeter's initial setup is easy.

Apache JMeter's deployment takes half an hour to one hour.

Apache JMeter is a free, open-source solution.

I recommend users explore each and every functionality of Apache JMeter.

Overall, I rate Apache JMeter a nine out of ten.

I use the solution in our organization for load testing.

The solution's automation capabilities are one of the best parts of the solution. Due to process automation, I don't have to prepare reports, making it the perfect solution. Whenever I require a report, the report gets generated by the solution, and then afterwards, I can look at the reports before copying and pasting them.

At times when we overload the application, it gets stuck. Especially with load testing, it gets stuck when we deal with huge numbers of 100 to 1,000-10,000 or 2,000 to 20,000. I believe that we should be able to hit around a million people without any issues. After the solution gets stuck due to overloading, we have to restart our computers. In short, the solution keeps crashing.

Apache JMeter is a simple solution, and I have been using it for seven years. Also, I am using the solution's latest version.

After an update in the application, the stability gets hampered if we continue to use its non-updated version, causing the solution to crash. So, once I faced that problem since I was not updating the application, it crashed. Back then, I wasn't aware that an update was available for the solution, which I had to apply to the solution. So, for two or three days, I tried to solve the issue with the solution. Later, I found that I just needed to update the application. So, after I updated the application, it started working fine. I rate the solution's stability a seven out of ten.

Since Apache JMeter is a scalable product, I rate the solution a ten out of ten. I am the only person using the solution in my organization.

Since I have experience with the solution's customer support team, I rate the technical support of the solution an eight out of ten.

Positive

On a scale of one to ten, where one is difficult, and ten is easy, I rate the solution's initial setup a ten out of ten.

The solution's deployment process took only a couple of hours. I believe it took me around an hour or so at the beginning during the initial setup phase. Right now, I can deploy the solution in fifteen to twenty minutes.

Maintenance for the application is only required when the application crashes due to its overuse.

Since we are using an outsourced solution, it is not paid for by our company.

My words to those planning to use the solution is that if the crashing issues in the solution get resolved, it is one of the perfect solutions in the market. Also, I have not used the paid version, so I have no idea how it works. It's a very resourceful solution.

I need to use the paid version to be able to comment on it. Since we are using the free version in a company, even if the solution makes any mistakes, we ignore those and go ahead.

Overall, I rate the solution a ten out of ten.

We use the solution for performance distributing testing.

The solution helps by detecting bottlenecks.

The solution provides a wide range of plugins and extensions, such as multiple monitors and multiple samplers. Apache JMeter can be used for multiple purposes, including performance and API testing, as well as integration testing. Additionally, users can create their own cloud and build their own distributor, eliminating the need to pay for any SaaS solution.

The UI has room for improvement.

I would like to be able to measure web performance as well using the solution. Apache JMeter is only for infrastructure testing, and backend testing, but we cannot use it for performance testing because we need to do it through the browser. 

I have been using the solution for one year.

The solution runs on Java software. 

I give the scalability a five out of ten.

The initial setup is straightforward. The documentation is very detailed.

I created a resource group in our private Azure cloud, and then I had multiple agents. This included one master and four or five slaves of Apache JMeter. I configured the Apache JMeter and began the distribution and testing.

I give the solution a seven out of ten.

I suggest using the solution and following the basics.

I've been using JMeter mainly for performance testing and some repair testing as well.

The solution is open source, so we don't have to pay for anything. That is a good thing since we can save the licensing costs, et cetera, as an organization. If you go for an expensive tool like LoadRunner or even Loyalty or Locust, you'll have to spend from your budget. JMeter has everything we need without the cost.

It's a powerful tool that is open source. There are various functionalities that can be used in various combinations. You can use Jmeter for automation, like getting some APIs. You can use JMeter for the performance testing. You can add listeners. You can look at the results and can generate a load with JMeter. The beauty of JMeter is there is a lot of support from the communities online who have worked on JMeter and can give first-hand advice. Most of our queries are already answered by someone, so we get the benefit of learning from them. 

It's a good tool for automated performance testing and some behavioral things.

It has a lot of customizable features. There are a lot of open libraries that you can download, and each time when you go for a new requirement, you will get new libraries. 

The setup is pretty easy.

The only thing is the learning curve. It's high.

We'd like to see more third-party integrations that can be handled quickly.

Support-wise, while the community is strong, it would be nice to have the option to reach out directly to JMeter. 

For performance testing, you need to correlate, et cetera, so we have to do it manually in order to get the right to regular expressions.

I've been using the solution for five years. 

As an open-source tool, when changes happen, it may be a bit unstable. This is occasional, and for the most part, it is fine. I'd rate it seven out of ten in terms of stability. 

The solution is scalable. I'd rate it ten out of ten.

While there isn't any traditional support, there is a very strong community around the solution. There are so many people using it and contributing to solving problems, you can easily find answers to your queries online.

The solution is straightforward to set up. I'd rate it five out of ten. There is a bit of a learning curve at first, however, once you start using it and taking advantage of its capabilities, I'd rate it nine out of ten. 

In the areas where we do some prototyping and also some areas where we want to save money and not focus on the revenue, we use JMeter. It's a very powerful tool. 

This is an open-source solution and is, therefore, free to use. 

I'm a customer and end-user.

I'm not sure which version of the solution I'm using. It's not the latest, however. It may be about one year old. 

You can deploy both on-premises and on the cloud. 

Once you go ahead and implement JMeter and you learn the process, it's a great tool. It could be a great asset for any organization as it is a highly customizable tool. If you can handle the learning curve, it will be worth it. Plus, as an open-source tool, you can save a lot of money on licensing. 

I'd rate the solution eight out of ten. 

Our primary use case for the solution is comprehensive performance testing. It measures how our applications are doing overall with a lot of users. For example, if we want to simulate 100 users doing transactions simultaneously, we want to see if our app handles it well and how fast it responds. In addition, we can utilize the solution to identify time spent on operations.

We find the ease of use and the reports and graphs available valuable.

The solution needs more metrics for reporting.

We have been using the solution for two years.

The solution is stable, and we have not had any issues.

The solution is scalable, but I cannot comment on the extent of its scalability because we have yet to scale widely.

We have not had experience with customer service and support.

The initial setup is straightforward.

We use the tool as an open-source tool, so we do not pay for it.

We chose this solution because of its affordable cost, ease of use, and popularity.

I rate the solution a nine out of ten. I advise users considering this solution to take a course to get familiar with it quickly.

The distributed load testing is very good and the ramp-up. When we come out with the right ramp-up plan, it can be converted into Apache JMeter script very well. This accurately simulates how many of our transactions need to be triggered.

I would like to see exceptions improved. The initial setup is complex and needs to be upgraded. It would be great to have additional protocols other than HTTP, HTTPS, and APIs.

I have been working with Apache JMeter for the past seven years.

The stability is good and I am not finding any issues.

We are not having any problems with the scalability of Apache JMeter

Technical support is very good.

Positive

The initial setup is complex.

Apache JMeter is a free tool.

I would rate Apache JMeter a nine out of ten.

The most valuable feature of this solution is being able to launch many requests and scheduling simulating human interactions with the application. There are some other plugins for monitoring and collecting data for JMeter but we don't use them. 

If JMeter could integrate with the EPM solution, it would be great. It could also be improved by offering more integrations for security. For example, most applications are secure with OpenID Connect protocols.

I have been using this solution for more than 10 years.

This is a stable solution. 

We previously used Katalon. 

The initial setup is straightforward. 

I would rate this solution an eight out of ten. 

We mainly use this product for load and endurance testing.

This solution is very user-friendly, and allows for a lot of data capture when testing.  

We also found that the test scripts that the system automatically generates are extremely well created.

We would like more documentation to be provided for the advanced level features that are available in this solution, in order to improve development.

We have been using this solution for two to three years.

We have found this solution to be very stable overall.

We believe this to be a scalable solution, although we have not made any amendments in user numbers to date.

The initial setup of this solution was very simple; the product is open-source, so only requires a download in order for the implementation to be executed.

We implemented this solution using our in-house team.

This is an open-source solution, so there is no requirement for licenses.

We would recommend that any organization using this solution for test script development, may also want to look for a complementary product to handle script exhibition.

I would rate this solution a seven out of ten.

Regardless of, whether it is used for personal performance, load, volume, UI test, or functional test Apache JMeter is the best tool on the market.

It is cost-effective and simple to use.

Take, for example, a performance test with, the Micro Focus performance test tool, and compare it to Apache JMeter. Apache JMeter is far less expensive than HP Performance Center.

When you run tests with JMeter, it generates test version five, which is extremely large. Also, when you have a large number of tests to run, it requires a large size or memory size, which basically means it consumes a lot of memory. It would be helpful to come up with a way to be able to use Apache JMeter in a way where it did not use as much memory. It will be much easier, and beneficial for the individual to run it on their own machines rather than having a high-end infrastructure, more CPUs, or more memory that has been consumed by Apache JMeter.

I have been working with Apache JMeter for two years now.

I am working with the latest version.

It's on digital platforms rather than the cloud.

I am absolutely satisfied with the stability of Apache JMeter.

Apache JMeter is a scalable product. We are pleased with the scalability of this solution.

When we have encountered difficulties and reached out to technical support, they respond very quickly and most of the things are readily available with them, for all of the challenges or support that are required. If I had to rate them from one to ten, I would rate the technical support an eight out of ten.

Positive

It is very easy to set up. There have been no issues, it's hassle-free, and it doesn't require a lot of expertise or specialization to configure and set up JMeter. 

It is very straightforward and very easy. That is something that anyone can do.

Our team completed the deployment. It only requires one person and takes no more than two to four hours.

In terms of maintenance, we only require one person.

When you compare it to HP because prior to using this Apache JMeter, we used this HP Performance Center, and in terms of ROI, while I don't have exact figures, when it comes to HP Performance Center, we have nearly five times more. You can say that it's five times less of an investment and five times written on the investment by using Apache JMeter. With Apache JMeter, you receive five times more. It's higher.

It's a yearly license.

I would rate Apache JMeter an eight out of ten.