Apache JMeter Reviews

We utilize it solely for load testing and performance testing. 

JMeter is user-friendly, and that's a notable advantage of JVTech. It's straightforward and easy to use, unlike some other load testing tools, making it very easy to understand.                

I have been using Apache JMeter for the past 4 to 5 years. 

The last time I used it, there were some APIs that I tested, and they were running well before. We didn't make any changes to them, but when I tried to check them again recently, they didn't go through. It seemed like an issue at the integration level. I'm currently working on getting half an automation, where I'll have separate linear and rest. But that's the situation so far.

I prefer tools that I can easily teach people within twenty minutes, and JMeter falls into that category. It's part of the tools I use to help others learn load testing. While JMeter can be a bit tricky, I find it easy to grasp and teach. It's user-friendly, and I can quickly introduce someone to it. It's a tool that I can easily exchange with others, and I aim to achieve proficiency in it soon because of its simplicity and ease of use.

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.

I use JMeter for concurrency and some backend services. We are also using JMeter to apply our tests within our framework by sending some requests to JMeter to assess our application's performance. My company is developing software based on data analytics that produces insights and graphs like Tableau or Power BI. We use JMeter to test the graphs, how the tables are rendered, and how long it takes to render some applications. 

For instance, we have a problem with one of our clients that use some complex scenarios or queries that take too much time to retrieve from the application or render to the end user. We ran a couple of tests on the application using JMeter and spotted the service or request that was taking too much time.We alerted the developers about this, and they took the appropriate action to fix this problem. Afterward, we run another cycle of JMeter to ensure everything is working as expected.

There are two modules. The analytics module is the interface for the stakeholders and company decision-makers. The number of users isn't that big, unlike the retail applications websites. It's 500 users at most. The other module is deals with data volume. We are currently doing some POCs to check whether we will benefit from JMeter in this area because it's not a concurrency issue. It's a data volume issue.

We have a hybrid deployment because we are using JMeter to assess the performance of our products. If the product is deployed on the cloud, we use JMeter on the cloud. If it's on-prem, we are using it on-prem. At my previous company, we mainly used JMeter on-prem.

I expect that we will continue to rely more on JMeter, and we have multiple DevOps pipelines using JMeter to test another module in our application.

I use all the tools, but one feature that stands out is JMeter's ability to test when services are sending a particular kind of request. We are using specific ports to send queries, and assess the performance based on the time it takes these queries to respond. You can use it with stuff other than the web performance.

The UI needs some work. The first time I used JMeter, I couldn't record the full scenario to mimic the user experience. Since then, they have introduced some plugins and a third-party tool called BlazeMeter. It's working on this, actually.

It's an excellent plugin that you can use to record the scenario from Google Chrome, and it integrates easily into JMeter. They could also make it easier to generate the built-in report. Now, you run the tests and generate the charts in a separate column. The graphs and charts that display the test metrics could be better.

I worked with another tool called Web Performance Tester, and its interface is better than JMeter's. They have intuitive graphs while you are running the tests, so you can see how things are going. It shows you the number of concurrent users logged into the system, the number of failures, response times, etc.

I worked in performance testing from 2011 until 2019. I was working with another tool, but in the last few years, I started using JMeter for a couple of projects.

It's hard to say definitively. When there's something wrong with JMeter, we're unsure whether it's something in the device because there are lots of requests coming from the machine. Maybe we didn't use it that many times from our local server. There are some bottlenecks, but in many cases, we only need to restart JMeter, and it works fine.

JMeter is scalable. I did a test using it in a distributed environment with more than one client. We used JMeter to load from the server and also the plugin tool. It works fairly well in a complex environment. I still need to research the maximum concurrent JMeter can handle. Is it 1 billion or 10 million? 

In my work experience, I need to load maybe 1 million users. For example, most of my work is on the backend of e-commerce websites with a maximum of 1,000 users. We have many clients, but the load is not that big. 

I don't think JMeter has technical support because it's an open-source application, but there is support for third-party apps that use JMeter. For instance, BlazeMeter has good technical support.

I have more experience in a tool called Web Performance Tester, but it has some limitations. For example, it doesn't support some forms. A long time ago, their support was better, but lately, their support hasn't been so good. They always ask us to switch to the consultancy service and they don't give us the solution. If we face problems, they always tell us, "Okay. You can consult us." This is not a good practice, actually.

Also, Web Performance Tester isn't well-known, so some of our clients aren't confident in it because it doesn't have a reputation.  They were more familiar with JMeter, and it's something I've used.  However, I have no problem with Web Performance Tester. It's hard to compare the two tools because it's not apples to apples. 

I joined this company in October, and they had just started using JMeter. Previously, they were using a tool that they had developed in-house. They found that JMeter has more capabilities and specificity than the tools they were using.

Setting up JMeter is straightforward. It doesn't need an installation like other tools. There is a batch file for Windows. Around four people in my organization are responsible for maintaining and managing JMeter.

JMeter is a free open-source tool. There are some third-party tools built on top of JMeter that have a license or something like BlazeMeter. I think you can also purchase some additional services.

I rate Apache JMeter eight out of 10.  Before using JMeter, you should find some tutorials because you need to be trained to use it. It's not a plug-and-play tool. This is what I did. Spend some time researching JMeter's capabilities. We met a lot of people who knew about JMeter, but when you tell them that it can do something, they're not aware of it. 

For instance, through taking some courses, we learned that JMeter has distributed performance capabilities. Some people still know that you can't make these recordable scenarios. This information hasn't reached everyone in the IT market.

Any front-end technologies like Angular, React, or others might access the services. Therefore, you must ensure that using SAP with JMeter works fine. Unless you ensure this, the front-end team may not access the services properly.

You can save the state of your tests and test plans after conducting tests, allowing you to showcase the results to others later. This feature makes it easier to demonstrate what testing was done and share those test cases.

From an improvement perspective, consider a scenario where your application needs to retrieve data from PayPal and store it in an Excel file in an external network. Connecting to such a source using JMeter might take some time. Previously, you might have linked your application to a server to obtain these results. However, achieving this kind of integration directly in JMeter can be challenging. If it were possible to configure JMeter to handle such server connections seamlessly, its capabilities would greatly be enhanced.

I have been using Apache JMeter since 2004-05.

It is a stable tool and has been stable for a long time. Organizations have been using it extensively since 2017. However, it's important to note that while JMeter is excellent for testing the performance of your service, you cannot directly forward the results to the end user.

You can increase the testing scale. When deploying a microservice in a production environment, performance testing is essential. You should test to handle at least one million users, a minimum benchmark. 

From a developer’s perspective, if your service can handle one or two million users with a response time of less than one second, it is considered acceptable, provided the data is accurate. In production environments with multiple servers, response times might vary, but it is crucial to perform thorough testing in a local environment to ensure the system meets performance criteria. JMeter helps verify that the service can handle the expected load and deliver accurate results.

I am using Azure and GCP.

JMeter is easy to set up, taking about half an hour to install. However, the real effort lies in configuring and developing the tests, which can be time-consuming. 

If there is an update, it doesn't typically take long to come. They may release an upgrade within one or two years. If you have a test suite, it can be easily imported, and you can start using it. This process hardly takes more than half an hour.

Apache JMeter is configuring it properly, especially when dealing with SSL configurations. It can be tricky and time-consuming if you're unfamiliar with handling SSL certificates, keys, and JMX configuration. However, the process becomes straightforward if you know where and how to pass the necessary keys and configurations. Without this knowledge, you'll likely need to spend time researching and Googling how to set everything up. In contrast, if you're familiar with these configurations, setting them up in JMeter is quick and straightforward.

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

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.

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.

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.