Apache JMeter Reviews

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.

We are using this for performance testing and some automation. We consolidate the test data in our own systems and then use an API to send this data to JMeter. The software testing team then uses it to perform all the tests they wish to do. Nowadays, we are mainly focused on regression testing and working with that.

It works really well. 

To be honest, the UI could be more user-friendly. As a UX guy, I believe it's quite cold. The solution that I have nowadays is a very traditional one. So, there is room for improvement in the UI of Apache JMeter. 

I have been using Apache JMeter for two years. We have it in-house. It's a solution that my company has been using for a long time.

There are around seven users in my company using this solution. 

In terms of setup, it's quite simple. It has its benefits, but we are already used to it. In terms of experience, it could be nicer, to be honest. Sometimes, I get a little bit lost.

Two people are required for the deployment and maintenance. They can be he managers, tech leads, engineers, or developers.

The users need to pay for licenses.

We are not switching because we have several testing teams, and we sell them to several customers. So the solution sometimes is not ours; it's the customer's, and they provide some licenses because usually, companies like Vodafone have corporate licensing. They can provide licensing without being responsible for it. 

We also have our own solutions, but we are not sometimes responsive before saying I don't want to use this or I don't want to use that. Because we are an outsourcing company, we put people accordingly to the field desired by our customers. So if I need a Selenium expert or an Optimum or TestRail, whatever, I go to the market, and I outsource this to the customer.

Overall, I would rate the solution a seven out of ten. I recommend it because I know a lot of people who use it, and they don't have any complaints.

Load testing is something that we used to do on Apache JMeter. We have regular releases every two weeks with varying features and modules. For major releases, where most of the EPS are modified or new features are introduced with new pages, we perform a performance test once every three to four months. We have a fixed schedule for performance testing before the sale, such as Thanksgiving and Black Friday, to ensure stability and performance during the sales period.

It is an open-source tool that is easy to use. It can be easily integrated with multiple tools, including Selenium. The tool also provides a recording and playback feature, along with the ability for modification and parameterization. Since it is an open-source tool, it can be easily integrated with many other tools, such as BlazeMeter, making the integration process very helpful.

The UI of the solution needs to be better. The UI takes up a lot of our bandwidth. So, we always run on the command line. Hence, improving the UI is needed. If it can be more lightweight, the editing can also be made easier.

I have been using Apache JMeter for four to five years.

Apache JMeter is a stable tool. Around 10,000-12,000 users are using the tool. One can increase its usage, but we haven't done so since we will need multiple machines to be connected to a network to generate the load. So, we haven't exceeded its use beyond 10,000 users.

Apache JMeter is a scalable tool.

We haven't used the solution's technical support.

We used other solutions in the past, but they were costly since they require a license, whereas Apache JMeter is free. Hence, we prefer Apace JMeter.

The solution's initial setup process was straightforward since setup can be done by opening a JAR file. It can be deployed in half an hour. Experienced people can deploy it in 15-20 mins, and newer ones may take up to an hour.

Also, we don't deploy on any server. Normally, the tests are on local ones.

For deployment and maintenance, you need knowledge of scripting and APIs. But otherwise, maintenance should be easy. Once you record and have the script ready, until and unless there are modifications to the application, maintaining it should not be much hassle.

The implementation was done in-house.

There is no investment as such. Only the resourcing part is there in the tool.

Apache JMeter is a free tool.

I recommend Apache JMeter to others who want to use it. I rate the overall solution an eight out of ten.

My clients are using it for BI reporting dashboards and executing dashboards. It's basically a reporting tool.

There are many features I like in Apache JMeter. First, it's open source, so I like that about the product. And there's a lot of community support for it.

There are some challenges in terms of recognizing the objects in some critical cases. These are object identifiers because Apache JMeter cannot recognize those dynamic objects.

I have been working with Apache JMeter for 12 years. It has been a long time. 

It is a stable solution. I would rate it a nine out of ten. 

It is an evolving product. It is a scalable tool. I would rate it an eight out of ten. We have medium-sized clients.

Most of the time, we get the solution from the open-source community. However, I have never interacted with Apache's customer support. 

The initial setup is very easy. We always use the latest version. It doesn't take much time to deploy the solution. 

It's a matter of hours to run a full test. However, it may take some time if you need to configure a project and create the skill to run it. Debugging can also be time-consuming. To set up an end-to-end process, it may take several days.

One or two people would be enough for the deployment. Someone from the infrastructure team can provide support in case of port issues, connectivity, or technical challenges. 

I have a different technology stack, such as BI tools like Tableau, Microsoft Strategy, and custom data applications. In some cases, I feel that Apache JMeter is not suitable. So, I am looking out for a different tool.

One tool cannot fit into all kinds of applications and business use cases. But by and large, it can cater to many applications. Overall, I would rate the solution a nine out of ten. 

We use the solution for performance and security testing.

The solution's most valuable feature is its ability to install and automate functions with ease.

They should improve the solution on its UI front.

 We have been using the solution for six years.

I rate the solution's stability as a seven or eight.

We are an enterprise business using the solution. It flips a bit whenever we add more than 10,000 virtual users to the solution. It becomes impossible to get the expected result. We have to use distributed testing to deal with the issue. I rate the solution's scalability as a six.

We check with the solution's community support forum in case of any queries. It is very active.

We tried out solutions such as LoadRunner and NeoLoad. As these were commercial tools, we settled for JMeter. Also, the reviews from those who have used the solution helped us switch to it.

I rate the solution's initial setup as an eight. It is easy.

Regarding deployment, you have to download the installation file and save it in the system. If it has specific prerequisites, such as installing Java, you need to ensure it is compatible with JMeter's current version.

The solution is free of cost as it is open source.

The solution works well for small or medium applications but not with 10,000 or more footfall. I rate the solution as a seven.

Apache JMeter is utilized for load testing of applications such as APIs and web services. Various types of load testing can be conducted, including stress tests and load tests. It supports different types of protocols, such as HTTP, HTTPS, SFTP, and others.

The most valuable features of Apache JMeter are user-friendliness, large resource, and the quality of assistance they provide. Additionally, it is easy to integrate with cloud platforms, such as AWS.

Apache JMeter could use improvement in reporting. Currently, it isn't easy to generate reports in PDF format. While receiving reports in PDF format is possible, it requires a lot of customization. Additionally, when comparing the load test to others solutions it could improve.

I have been using Apache JMeter for approximately five years.

Apache JMeter is a stable solution.

We have more than 100 people using Apache JMeter in my organization.

We have multiple clients using this solution and all of our testers are using the solution.

My advice to others is for them to go through online tutorials before using the solution. It is easy to use, and anyone can quickly learn and test their application.

I rate the scalability of Apache JMeter an eight out of ten.

I have not contacted technical support.

The initial setup of Apache JMeter is easy and simple to configure. The whole process of implementation takes approximately half an hour. The first step is to download Java and install it. The last step is to download Apache JMeter and install it. 

The main reason we chose Apache JMeter is that it is cost-effective and easy to use. There is no need to pay for additional services. Additionally, it does not require additional payment to vendors. The solution is open-source and free.

I rate Apache JMeter a nine out of ten.

We have a Neotys slave server configuration where we have one server that caters to three servers, and we test most of the load on Apache JMeter, particularly for a hundred users. We test the load for web applications, services, and the rest of the APIs, though our current setup for Apache JMeter isn't that big.

Initially, Apache JMeter had a complex configuration; its UI was tricky and required a lot of resources. Creating scripts and running tests on Apache JMeter was always confusing, but nowadays, with more documentation and UI enhancements, Apache JMeter has improved. Previously, recording and creating scripts was tricky, and you had to do it manually. Now there's a recording facility in Apache JMeter that lets you create and modify scripts and test faster, which helped improve my organization.

To me, what's most valuable in Apache JMeter is that it's a lightweight tool for application testing. It's the best load-testing tool for my company because Apache JMeter simulates your application during testing. Apache JMeter also creates threads with good server utilization. Apache JMeter allows you to focus on analyzing the situation, looking into measurements, response time, and client-server responses, which I find valuable.

Both scalability and stability could be improved in Apache JMeter.

What I'd like to see in Apache JMeter in the future is ease of use in terms of scripting. A recording capability similar to what LoadRunner offers, where you can record scripts, make some modifications, then the script will be ready, is another advanced feature I'd like Apache JMeter to have. The two features would make it easier for new users to learn how to use Apache JMeter and help users utilize the tool more quickly.

I've been using Apache JMeter for more than six or seven years.

Apache JMeter isn't as stable because it sometimes crashes when you're running a test. The performance of Apache JMeter could be improved because testing on it isn't always as smooth sailing.

The tool is partially stable. You can't expect Apache JMeter to run well for enterprise-level, high-load applications. It's a good tool for more straightforward or lightweight web applications but not for CRM-type applications.

Scalability-wise, Apache JMeter could be improved because if you try to implement it on multi-servers, the threads running on the tool don't hold up well.

We used LoadRunner before using Apache JMeter. As Apache JMeter is open source, and we only needed to test lightweight applications, we were pretty sure we wanted to go with Apache JMeter.

Apache JMeter is an open-source tool that you can install directly from the web with binary files, so setting it up on one to two machines is easy. The setup could be tricky if you hook Apache JMeter to three or more different machines, and it's also tricky when you execute it after.

We implemented Apache JMeter in-house.

I've seen ROI from Apache JMeter, mainly because it doesn't cost much to maintain, and we can use it on a few lightweight applications.

We didn't pay licensing fees for Apache JMeter because it's an open-source tool. We only paid for the machines where we installed Apache JMeter modules.

I have experience with Apache JMeter, with version 5.5. as the most recent version I've used.

Apache JMeter is deployed on-premises, but my company did a POC with Apache JMeter and BlazeMeter. BlazeMeter is a CA proprietor tool where you can hook up Apache JMeter scripts. BlazeMeter is a cloud-based tool where you can run tests with the help of Apache JMeter scripts.

At the moment, only two people use Apache JMeter within my company. Two people can handle the deployment of Apache JMeter, while only one person is required to maintain it.

My advice to people looking into implementing Apache JMeter is to make the decision based on the application portfolio. For example, if it's more diverse, then using Apache JMeter could be tricky, but if you're only testing lightweight applications, Apache JMeter will be a viable solution.

Apache JMeter requires minimal investment, yet it has some returns, and it's a good tool, so I'm rating it as seven out of ten.

The primary use case for the solution is to test web applications.

The most valuable feature is that the solution is open source.

There are a lot of areas in this solution that can use improvement. The solution is not user-friendly, there is no framework for autocorrelation or parameterization.

I have been using the solution for a little over one year.

The new version of the solution is stable.

The initial setup is straightforward as long as you do not require an advanced setup, which can be difficult. The basic setup takes only one hour.

The solution is open-source.

I give the solution

The only support available for the solution is online because it is open-source and does not come with technical support.

To anyone that is thinking of using the solution, I suggest you familiarize yourself with regular expression.

We've been using Apache JMeter for load testing, spike testing, and endurance testing. We use the solution mostly for nonfunctional use cases, except for the security aspects, because those aspects require a different tool altogether.

What I like best about Apache JMeter is its user-friendly GUI because even if you don't have very good coding knowledge or understanding, or even if you don't come from a development background, you can still use the solution with just a few clicks. This is what's unique about Apache JMeter, in comparison with other tools in the market.

As Apache JMeter is open source, when there's a missing feature, you can search in several community blogs for plugins that you can use to modify Apache JMeter to meet your requirements, and this is another advantage.

What needs improvement in Apache JMeter is the very high load requirements when you want to scale it beyond certain thresholds. For example, small to mid-range testing is very easily done with Apache JMeter, but if you scale and increase the load, then it would be a problem because the tool consumes a lot of resources, probably because Apache JMeter provides an enriched UI experience, so it consumes a lot of memory and requires high CPU usage. This means you have to manage your infrastructure, or else you'll have high overhead expenses.

As Apache JMeter is a heavyweight tool, that is an area for improvement, though I'm unsure if Apache can do something about it because it could be a result of the way it's architected.

What I'd like to see from Apache JMeter in the future is for it to transition to the cloud, as a lot of cloud technologies emerge around the globe, and a lot of people prefer cloud-based solutions or cloud-native tools. Even if a company has a legacy system, it's still possible to transition to the cloud. I've worked with a company that was an on-premise company that moved to the cloud and became cloud-native. If Apache JMeter could transition to the cloud, similar to k6, then it could help lessen the intense resource consumption that's currently happening in Apache JMeter.

I've been using Apache JMeter since 2020, so it's been two years since I started using it.

Apache JMeter is a stable product overall. A very large community in the software industry uses Apache JMeter, and though it's open source and there's a continuous phase of improvement going on with it, it has stable versions available for my company to continue testing it.

Apache JMeter is scalable in the sense that there's a master/slave architecture available for it where I can scale as many slaves along the way, but when a huge number of users is required in a particular load test, and you have to scale a lot beyond a particular threshold, the resource consumption becomes too high and requires considerable overhead. Apache JMeter consumes a lot of memory, and that's a hurdle, but it's scalable up to a certain point. If a very, very large organization requires very heavy load testing to be done, it would be better for that organization to go with some other tool.

Because Apache JMeter is an open-source tool, you get support from the community. The challenge with open-source tools is that if there isn't enough community, then the support and development you get would be limited, but as Apache JMeter is widely used, the community is vast and the support is sound. Unlike with Micro Focus LoadRunner, when you encounter an issue, you can report that to Micro Focus and the Micro Focus team will take care of your issue. It doesn't work that way with open-source solutions.

For the support I get from the community, on a scale of one to five, I'm rating it a three because there could be instances where you could not get a resolution for your issue. After all, Apache JMeter is a free product, so you can only rely on community support. Though the community for the tool is so big and Apache JMeter is widely used, and there'd be a lesser amount of circumstances where the solution for your issue isn't available yet, there could be between one percent to five percent chance of it happening, so that could be troublesome.

The initial setup for Apache JMeter is pretty simple. There isn't much dependency, in general. For example, in macOS, you can just download the tar files entirely and just untar the files. There's no installation of specific extensions required. That's for macOS. For Windows, there would be .exe files. From that perspective, setting up Apache JMeter is quite easy. You can just run it locally, untarring it in any particular location. Just one setup that's required to be done is setting the Java home path to start the app. Otherwise, it's pretty straightforward and very quick to set up.

On a scale of one to five, I'm rating the initial setup a four because there's always some room for improvement.

Apache JMeter is an open-source solution, so it's free to use.

I evaluated k6 and Locust.

I'm using Apache JMeter for work. Locust is also used within the company, as well as k6, but I only touched base on those solutions.

The projects I'm working on currently use Apache JMeter, but my company works across regions and uses different tools, including Gatling and Locust.

Apache JMeter is used daily, for the range of projects I've been testing it on. A new government project came in, and I chose Apache JMeter for it because of its simplicity and user-friendly interface.

My rating for Apache JMeter is seven out of ten.

Our company uses the solution for performance testing on web applications, API load testing, and automation of APIs and web applications. The solution provides three streams of use. 

We also integrate Selenium with the solution to perform automation testing. 

The solution has good transition controllers and distributed testing. 

The solution's setup could be easier and security could be improved to minimize vulnerabilities. 

I have been using the solution for four years.

The solution is used to test the stability of other applications through a three-step process. 

Load tests look at the CPU, memory, and APM tool and assess the current load to determine if it can be increased from 60% to 70% for example. You continuously monitor the APM to see fluctuations in memory and CPU usage. If load tests are successful, then you move on to stress tests. 

Stress tests find bottlenecks and determine how many users the application can handle within the current infrastructure. Baseline tests can be performed to determine results such as response time when increasing users. 

Endurance tests determine if an application is stable and for how long stability can be expected. For an endurance test, you set up a particular user load and run it for at least eight hours but up to twenty-four hours. During this time, you see how the application is behaving and whether the CPU and memory are stable. This will allow you to assess overall stability without OOM leakages. 

The solution determines if there are lags in application performance. For one project with 500 continuous users per hour, we used the solution to find that there were only two lags from 50,000 samples generated.  

The solution is used to perform baseline tests for applications and compare them to SLAs to determine user load and scalability. 

I have not needed technical support. 

The initial setup can be complex depending on the application you want to test. 

If the application is straightforward without much logic, then setup is easy and only requires a simple transaction controller. This scenario is common for users who log in, perform simple actions within 15 minutes, and log out. 

Applications with internal logic require scripting that includes sample JSON extractors, pre- and post-processes, transition and throughput controllers, and precision throughput timers. This scenario is common for users who perform multiple actions over a longer period of time, is not straightforward, and involves multiple transaction controllers. 

Our company implements the solution for customers.

First, we ask our customers about critical work flows and categorize them based on user loads to create a workload model. Then, we create scripts and proceed with testing. 

Often, we request access to a remote desktop for installing scripts and resetting networks. We follow the workload model to initiate load, stress, and endurance tests. 

The solution is open source with no user fees or licenses. 

The solution is comparable to LoadRunner because it works with multiple plugins but is free to use. 

I recommend the solution and rate it a eight out of ten. 

The solution is open source so on occasion there are security vulnerabilities.