Apache JMeter Reviews

We use this solution to load test functional behavior, and measure performance.

We really appreciate that the solution comes with a live community, which continuously provided plugins and support protocols.

We would like some reporting and analysis tools to be added to this solution.

We would also like the manual available for this solution to allow for better usability; it can be quite complex for new users, and the product is not always very intuitive. 

We have been working with this solution for 12 years.

We have found this solution to be a stable and reliable tool.

This solution is easily scalable, you can distribute the larger generation among several machines in the LAN, or you can use the cloud variation of the product.

This solution doesn't come with technical support, but there is plug-in wide community support, where organizations can ask questions about issues they are experiencing.

This solution isn't actually deployed, it is a zip file, which is extracted. It can also be deployed via public cloud, if an organization chooses the cloud-based model.

This is an open-source solution, so there are no licensing costs involved.

We would recommend that organizations considering this solution invest time in research of the product before implementing it. There are a lot of online resources that can assist with this, so the business can check if the solution will meet their requirements.

I would rate this solution an eight 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.

We are in the service industry. We implement it for our customers. We recommend the right tool and set it up for them. So, I've not had any hands-on experience in my current role, but I have a good understanding or a fair idea of the tool's capabilities. I have a team that takes care of the technical aspects.

It is an open-source solution. So, typically when you don't want to make a heavy investment, and you want to do some level of performance testing, Apache JMeter is used. 

It is typically on-premises, and it has also been on the public cloud. It could be Azure, or it could be AWS. It is very rarely on GCP.

It helps them to look into several parameters. For example, when you have certified test cases that are predominantly repeated on an application, you can execute the same thing with increased load. You can see how the application responds and if there is an impact on the response time of the application. You can confine it to certain parameter conditions and then start making changes to see how it performs. You can see where the RAM or CPUs are stagnant and not increased.

The metrics part of it and the ability to write your custom code to do some specific tests in the performance testing space are the most valuable features.

It is easy to use. If you want to test your application out and not incur a lot of costs, it is probably the best tool.

Its reporting could be improved. There should be a better visual representation. That would be helpful for easy consumption of the reports.

I have been using it for about four to five years.

JMeter is probably good for lower loads. It is not comparable to LoadRunner when it comes to higher loads.

It probably scales up to a few thousand users but not beyond that.

Because it is an open-source community, their support is probably average. It won't be like the support for a commercial product. I would rate it a six out of ten.

LoadRunner is one of the prominent tools. It was formerly HP, and now it is Micro Focus. It has good capabilities and features. It also has decent reporting capabilities. Because of the brand and the capability, it was probably chosen by most of the Fortune 500 clients that we work with. There are also some startup communities or organizations that ventured into other solutions, such as JMeter.

In terms of comparison, primarily, there are three to four parameters. The first one is the ease of use. The second one is about the protocols that need to be tested, whether it's web or API, HTTP, HTTPS, and all the native things. The third one is in terms of flexibility in setting it up and executing, and the fourth one is in terms of monitoring the execution and reporting pieces. Those are the key parameters for pros and cons. LoadRunner gives you a lot more capability and flexibility, but at the same time, it also consumes a lot of resources. JMeter is relatively simpler, cheaper, and easier to use.

I don't have hands-on experience with it, but based on what I have heard from people, it's pretty straightforward in terms of the setup. 

The setup probably takes a week or two, and then the execution is probably a three to four weeks exercise.

We are in the services business. Clients give us access, and we set it up there.

It is certainly good for testing out the applications for performance testing, especially when you have to test them out frequently and make sure that they are good for at least a few thousand users. It has a decent ROI.

It is open source. There are no licensing costs associated. If you need enterprise support, you'll probably end up paying for a license.

You would also factor in the infrastructure cost, but that's not significant.

I would rate it a seven out of ten. It is a decent choice from a small-scale perspective, but reporting could be better. If you want to get some performance testing done without spending money, JMeter is probably the best tool. It doesn't have the best reporting, but it is quite a handy tool.

We are in the financial industry in India and carry out performance testing. We deal with  SWIFT messages and financial messaging systems. A few years ago we had 2 million transactions in five hours; today it's 2 million in two hours. To measure these performances, I use JMeter for regression. We have Exadata, Exalogic infrastructure. We are users of JMeter and I'm a technical specialist. 

This tool is very user-friendly and easy to use. It's open-source so there are no costs involved for the non-production environments. It's easily available to anyone who wants to use it and it has all the features required for performance metrics.

I think it has some proxy-based dependencies which require specific proxies to be set up or disabled, which causes problems when we are working in certain specific environments that have a proxy setup. When we want it to do a record with some new scripts, there are some challenges there.

I've been using this solution for two years. 

The solution is stable and easily scalable. 

The support is very good, with good technical teams. Whenever we get stuck they support us and provide solutions. 

The initial setup took only 10 minutes but there were some complications with the product initially having less features. That has been greatly improved. It's easy to do maintenance of the test tools which we develop, and it's easy to maintain as a product. We have around 20 users of this solution. 

It's open-source, so there's no cost. If you need some support from the vendors there will be a charge for that. 

I would recommend this solution. Most of the support, guides, and tutorials are available on YouTube. 

I rate this solution an eight out of 10. 

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.

We engage in performance testing using JMeter based on the client's requirements. We decide the endpoints for JMeter based on the domain and application requirements. The requirements, like 50 users per minute or 500 users per hour, guide our performance testing framework.

JMeter has allowed us to effectively verify that, based on pre-requirements, performance standards are met. Since it's an open-source tool, it also allows us to reduce the expenditure on performance testing tools.

The different listeners in JMeter provide various reports and results. It's very useful for performance and load testing. Its compatibility with external tools, such as the ability to import scripts from Selenium and Azure DevOps, makes it a robust and flexible option.

I would recommend the inclusion of plugins for AI in JMeter. Some features still require a certain knowledge level to use effectively, and making these features more user-friendly would be beneficial.

I have not been a direct team member but have managed a team working on JMeter for almost eleven years. In my nineteen years of experience, I have engaged with performance testing, with JMeter being part of our toolkit.

Stability is not a concern for expert users of JMeter. However, stability can be an issue for beginners.

JMeter is widely used and very scalable, rated between eight and nine in terms of scalability. It can also integrate with cloud solutions like Microsoft Azure.

There are many online blogs, forums, and video tutorials available for JMeter, providing substantial support for both beginner and intermediate levels.

Positive

LambdaTest and BrowserStack were part of our working user experience, but not extensively more than that. I initially worked with other performance testing tools like LoadRunner.

The setup for JMeter is very easy. There is no installation required; it is simply a package that needs to be imported and can be set up within half an hour or less, depending on the download speed.

Our clients cover the necessary licensing costs, particularly when using cloud services like Microsoft Azure.

JMeter itself is an open-source tool, so there are no licensing costs associated when running on-premises. Client-covered SaaS licensing, such as with Microsoft Azure, does not involve any costs on our side.

It's important to be very skilled in manual testing concepts before starting with performance testing. Due to JMeter's advanced level of techniques and skill requirements, extensive hands-on experience with real-time projects is needed. It generally takes three to four years of practical experience to master.

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 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.