Apache JMeter Reviews

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.

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. 

I am using this solution for a banking use case. We have an older version of this solution. We are planning to upgrade to a newer version.

A lot of things are valuable. It is free. It has a lot of features, such as report generation and integration with CI/CD, which makes it very competitive with the other paid solutions available in the market. It is a good solution.

They can improve it a little bit in terms of distribution load testing. We struggled with it during the distribution. 

In terms of reporting, runtime monitoring is not currently included, and it should be included. They can also improve it on the reporting side in terms of the comparison of the reports. 

They can also focus more on integration with CI/CD. Currently, people are using their own customized tools. It would be nice if Apache can provide some standard tools and procedures for integration with CI/CD tools like DPR. There are some tools, but it would be nice if official standard tools and procedures are available.

I have been using this solution for almost three months.

It is stable. There is good support, and fixes are also available immediately.

We have not scaled it, but it is scalable. We plan to increase its usage. 

I didn't have to call Apache because if anything comes up, we are able to find a solution in the community.

Its initial setup was straightforward.

We are using the free version, and if required, we can easily switch to the other version.

I would definitely recommend this solution if it suits a use case. It is good, and it also looks promising. We plan to keep using it in the future.

I would rate Apache JMeter an eight out of ten.

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.

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.

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.

I mainly use JMeter to capture the traffic of the most-visited page to see how much load a particular page is getting and how many users are using that page for a particular amount of time. I've also used it to capture APIs for particular pages.

The most valuable features are the ability to capture the entire traffic of particular pages and the proper readability of entire pages and entire APIs.

One of the drawbacks of JMeter is that it can't handle a large amount of load, which forces us to switch to other tools when we need to load more than a 5,000 or 10,000 user load. In the next release, I would like JMeter to be more compatible with other languages in the market.

I've been using JMeter for six to eight months.

JMeter can't be used in the long run, so I'd rate its stability as five out of ten.

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

Apache's technical support is pretty good, I've had no issues with them.

The initial setup was straightforward and took about five to six months.

I used an in-house team.

JMeter is open source, so there are no licensing costs associated with it.

I evaluated SoapUI, Postman, and Visual Studio. JMeter was more reliable compared to these options.

I would definitely recommend JMeter in terms of usability. If you're using AngularJS as a language for testing UIs, JMeter might not be a good idea. I'd rate this solution as six out of ten.