Apache JMeter Reviews

We primarily use the solution for performance and delivery testing.

It's a free tool. It's a very common tool. There's a lot of support in the community for this. It mainly supports web API testing.

The UI could be better. It can have some Reach UI also, which would be helpful, and maybe a relatively simpler way of using it. It needs simple modules. There are quite a lot of things which are kind of abandoned, so they can definitely improve on it.

Integration with some of the other features should be managed. However, it's open source, so there is not much to complain about there.

It's an open-source tool; we cannot ask for additional features really.

The product could use some kind of filtering and monitoring and different degree of dashboards and analysis. If that can be provided, that would be very, very helpful.

I’ve used the solution since 2009.

The solution is relatively stable. There are no bugs or glitches, and it doesn’t crash o freeze. It’s reliable.

It can scale. However, what others say about scalability is that you need to have some proper calculations to be done first.

We have dealt with support. Technical support is found in more technical forums. It’s open-source, and communes are where you go for information. We have received good responses when we have inquiries. There are quite a lot of forums in general available.

Now, as we have grown as an organization or as a team, there are still questions such as, "What are the limitations of this tool?" And we put that to JMeter so we can learn what is best for the maintenance.

The installation can be a bit complex. There are quite a lot of things and issues if you go deep into it and if you're setting up JMeter. For example, direct script captioning is slightly different. It's a bit more complex, the correlation parametrization. Setting up the workload model can be complex as it is based on a Java service mechanism.

It becomes a bit challenging to manage. If I want to put a 50,000 user load, I have to be very careful how the memory is utilized. I must be very aware of the underlying system's capability to execute this. I have to make it into multiple nodes and run them in parallel. There are some calculations, and there are some good power processes that will be required when you are using JMeter. You need to understand its limitations and load work them on.

The solution doesn’t really need maintenance. They're open-source tools, so we don't expect any maintenance. What we typically do is we pick up a particular version and understand the limitations of it. We then play within those limitations.

We handled the initial setup in-house. I handled the setup myself.

The solution is free to use.

We may be using the latest version. I don’t know the exact version number.

It is on-prem. However, we can put it on the cloud as well. We install it on any machine, so it can be a local or cloud-based machine.

I’d recommend JMeter. One critical piece of advice is to plan properly. For JMeter, planning and having an understanding of the limitations are important. If you play within those limitations, it is a really great tool. There are trade rules that apply to a lot of things that we use. However, there's plenty of material available so far. Whoever is doing it, can plan it accordingly. They can create those tests, and execute those tests. That said, at the same time, be aware of the scalability of the JMeter. For example, a single JMeter line, which is running, can take 1,000 to 2,000 threats, not more than that. Again, it depends on the available hardware. If you want to scale to, say, one million or something, different parts of planning are needed.

I’d rate the solution eight out of ten.

We have a couple of applications in banking.

It's an open-source tool, Apache JMeter. 

It's easy to customize. Customization depends on the requirements, however. It provides an enormous amount of plugins. Based on the customer requirements, we can customize our code and we can go out and execute the test. JMeter integrates well with Jenkins. The cloud offers CI/CD activity. 

The solution is scalable.

The stability is good. 

Its initial setup is very easy.

There is good documentation available. 

Until now, JMeter is not supporting most of the protocols. It's widely using web HTTP and a few other protocols as well, however, it's not supporting the SAP or Citrix ones. Protocol-wise, the JMeter needs to improve.

Recently, there was a Log4j error. They have since mitigated that, in JMeter, for the free version. The security concern was handled quite well compared to the previous versions.

I've been dealing with the solution for more than five years.

The solution has been stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

It's scalable. We have very good load balancing or load distribution. It will be very easy for us to add multiple machines and make whatever we need. However much we want, we can scale.

It is very easy to set up. It's not overly complex or difficult. 

The solution does offer a free version. 

I'd rate the solution eight out of ten.

Apache JMeter is quite flexible and it is also well distributed. It is quite flexible compared to Micro Focus LoadRunner.

JMeter is easy to script. There is less of a problem with doing correlations and parameterization. 

It is not something that can be compared with Micro Focus LoadRunner. It gives the facility too easily; you do things through UI. With JMeter, you really do not have any easy UI to work as, like a Micro Focus LoadRunner.

The stability could be a bit better.

Compared to LoadRunner, it hasn't any proper UI. Recording the script is also not flexible in JMeter. In LoadRunner, we have a couple of options, such as URL-based recording and HTML-based recording. In JMeter, it's not like that. JMeter has a recorder, however, it is not easy to use. It is a bit tricky to configure the automatic recording in JMeter. 

I've been using the solution for four or five years. 

JMeter, stability-wise, is good, however, it is being developed by the community. Therefore, stability is always an open question there.

The solution can scale a bit. It is scalable, however, not like LoadRunner. I have not tested it as such yet. I'm not sure about how fully scalable it is. 

I'm also familiar with Micro Focus LoadRunner.

The implementation process is not so easy. It's difficult to configure.

I'd rate the solution a seven out of ten.

I'm an end-user and a customer. 

We use Apache JMeter for performance testing, including the response time of our websites for multiple users.

The product is specialized in performance testing. It gives accurate results and recommendations that we can implement to enhance the performance of websites.

Apache JMeter could be a more user-friendly product from the end user's perspective. It requires someone with technical knowledge to administer it. This particular area needs improvement.

We have been using Apache JMeter for a year.

I rate Apache JMeter's stability a ten out of ten.

We have around 12 Apache JMeter users in our organization. I rate the product's scalability an eight out of ten.

The technical support team responds quickly to queries.

The initial setup process is very complicated for the on-premises version. It would be better to use the cloud version.

The product has reasonable pricing.

It is a complete tool that integrates lots of functionality. I recommend it to others and rate it 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.

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.

We use this solution for functional API testing, and performance testing.

This solution allows us to test all the functional APIs through it, then record and run the APIs.

This solution is easier to use than any other tool in the market; there is not even a requirement to learn a lot of scripting in order to use it.

We also appreciate that the solution is open source, so it has a very big community to utilize if we need help with an issue.

At present, if the number of virtual users increases beyond 10,000 when testing, then it results in a Java heap which causes the solution to crash.

I have been working with this solution for around seven years.

The stability of this product is good, outside of the issues with adding virtual users during testing.

This solution is scalable, but only up to a certain point when adding virtual users, before performance issues begin to occur.

The initial setup of this solution was quite straightforward, and deployment only took one to two minutes.

We implemented this solution using our in-house team.

This is an open-source solution, so there are no licensing costs associated with it.

We would recommend this solution to any QA or developer as a 'must-try product'.

I would rate this solution an eight out of ten.

The use cases are mainly for performance testing and for test case management of the different APIs.

Initially, we didn't have any tool for performance testing, particularly open source. JMeter, since it is open source, we can test our APIs pretty quickly and we can work with different teams to provide performance testing very quickly. It doesn't take up much of our time.

The ease of scripting is great. 

The modular design is very useful.

It is easy to set up.

The solution is stable.

It can scale well. 

If JMeter could provide a web version of editing, that would be good. 

If JMeter can provide its own cloud version rather than depending on BlazeMeter, the commercial version of JMeter, that would be ideal. If we could have somebody right on the front end of JMeter, using it on any of the clouds, including AWS, GCP, or Azure, that would be very helpful. it would be better than me going for using commercial services.

I would like to have some kind of cloud version that can be implemented. Or we would like a Docker version. A Docker version is something that I would look for.

I've been using the solution for four or more years. 

It is a stable, reliable product. There are no bugs or glitched. It doesn't crash or freeze.

The solution has been scalable. 

We have almost 100 users on the solution. 

We likely won't increase usage in the future.

I do have some knowledge of technical support. 

This is an open-source tool. If I write any issue in the forums, somebody will answer it pretty quickly. The open source technical support they have on offer is good.

We did use a different solution previously. 

Most people know JMeter more than the other tools. It's easy to learn and quick to execute. It's also open source. You can get a lot of solutions across the internet. If you are having some issue or error, somebody or the other may have faced that same issue, and he may have found out the solution. It makes troubleshooting easy, having crowdsourced troubleshooting. That was a factor in our decision-making. 

The initial setup is not straightforward. It's simple and not complex at all. 

We only need two people to maintain the product. It doesn't take a lot of staff. 

We have our own in-house team that can handle the setup. 

We've definitely seen an ROI. 

We use an open-source version of the product. However, there are cloud services that we use. I'm not sure of the cost of the cloud services.

We looked into Micro Focus and Cavisson NetStorm. However, they were licensed tools, and we decided against them. 

We are using the latest version of the solution. 

We are using a cloud version of JMeter that is called BlazeMeter.

If you are a company that is evaluating other licensed tools, just go for JMeter. It's open source, easy to use, and the most widely used across platforms. It would be much simpler than using the other licensed tools. Other licensed tools may have pretty good technical support. However, most problems with JMeter can be solved using the solutions that are available on the internet.

I'd rate the solution eight out of ten.