Apache JMeter Reviews

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.

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 use this solution mostly for creating scripts, load testing, and performance testing. If my client doesn't have a tool or I don't have a tool, I try to leverage JMeter because it's an open-source tool.

I personally use JMeter for things which cannot be covered by our load testing tool, which is OATS, Oracle Application Testing Suite. This is a tool that was developed by Oracle but is no longer in use because Oracle has stopped developing it.

The solution is deployed on-prem and on private and public clouds.

JMeter should be more stable. Every time there is a new release coming up, a lot of its older functionalities or the new functionalities that are brought in are not very well-documented. It should be documented properly, and there should be proper use cases. A lot of the newer features don't work, and sometimes you have to spend a lot of time maintaining the scripts. That is something JMeter could probably look at.

For example, in JMeter 5 they brought in a lot of new controllers. But there isn't a lot of documentation available on the Apache site on how you're supposed to use those controllers. They've explained the controller functionality, but there aren't any proper use cases to show that. 

I have been using JMeter for a long time and do a lot of work with this solution.

It's not stable. With every new release, they come up with newer features, which aren't always very stable. So, stability is a concern.

It is scalable. You can scale up to 1,000 users in JMeter. If you can put up four slave servers, you can easily ramp up to 1,000 users. That's not a problem.

Because it's open-source, a lot of organizations try to leverage JMeter into everything. I don't think JMeter is currently very adaptable to all the technologies. That is something Apache should think of – incorporating other technologies and other tech stacks, which can be scripted from JMeter and tested using JMeter.

On a scale of 1 to 5, I would rate technical support 2.5

They're not very good because JMeter is an open-source tool. You can raise a bug to JMeter, and they might fix it or they might say that, "We will actually fix this in the next release." So, because it's an open-source tool, you do not get dedicated support. You have to raise tickets and wait. If you use BlazeMeter, the support is probably a little better because you can take your issues there.

I don't think support is great if you compare it with tools like NeoLoad or LoadRunner where they have a dedicated support team. You can raise tickets. You have a direct conversation with their engineers. They can help you understand where the issue is exactly. That kind of support is not in JMeter, at least not now. BlazeMeter has it, but I have not used BlazeMeter support, so I'm not sure how it is. But from what I have seen with JMeter, support is not great.

It is straightforward, but for JMeter 5, since they have introduced SSL handshake at the slave level, that becomes a little bit of a challenge for somebody who is doing it for the first time if you're doing a distributed execution, that becomes a challenge.

But since there was not enough documentation, I had to do a lot of troubleshooting on my own, since it was new. Now there's a lot of documentation available, but initially, there was not much documentation.

JMeter is pretty easy to use if you are using it for the purpose of only developing scripts. You can just uninstall the file and you can start using it. The only challenge happens if you're trying to access the internet over any kind of proxy. Then, you'll have to start it via the proxy mode.

Otherwise, deploying JMeter is pretty easy compared to other tools. You just have to download, unzip, and you are ready to go.

We installed JMeter ourselves.

I would rate this solution 7 out of 10.

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.

I've used JMeter in conjunction with Selenium, Java, and Log4j for logging. I used it before
I ended that contract in August. Its version was up to date at that time.

It was used for an e-commerce site that is specialized in C-PAP or weaving machines in effect. Their max was a thousand people logged in at once. I, of course, pushed the boundaries on that, but it was to test the performance of the website, and of course, I'm had to try subsystems, database interactions, etc.

I'm a total geek, so I liked the fact that I got to program. The biggest thing I liked about it is that there is a huge user base out there, and being shareware and being Apache, if I have any question on how to get something done, I get 18 different answers. Out of those, there would be at least a few good approaches for what I was trying to do. So, the support system out there is most valuable.

I sometimes found the documentation to be not as explanatory as I would've liked it. In the cases that I can think of, I was looking for a rather hand-holding approach with Step A, B, and C, but then I realized that with a product that is open source like this, you can't do handholding. That is because there are so many different uses and different unique environments and setups for it, but I remember thinking a few times that if they only just said this.

If I were going to be Mr. Selfish and say anything I want, I'd say a full feature GUI that lets me drag and drop different modules in line. It could have a simple-to-use GUI.

I have been using this solution for probably a year and a half.

I didn't have any issues with the stability of JMeter itself. There were definitely issues with the program I was testing, but that's why I was testing it.

It was very easy to scale, but I was barely scratching the surface. I have spent 17 years at Microsoft, and for the performance testing that we did there, we had 8.3 million users at once, as opposed to a maximum of a thousand. If I'm scaling, I have to do it quite straightforward and simple, but it was very minimal.

Only I was using it. It was the QA department. I showed it to some of the devs, and they were very interested. A couple of them tried it, but none were actually using it day-to-day for testing out the environment.

I would rate them an eight out of 10 because sometimes, they would take two or three days to get back to me. Of course, at that point, you're like, "I need the answer; I need to answer." So, it was a little bit unrealistic in terms of expectations.

At that particular company, I was the one who was tasked with coming up with the solution, so that was the only one that I looked at simply because JMeter is industry standard, but at Microsoft, they wrote their own custom tools, so I used custom Microsoft tools.

It was rather complex. It is a complex product, but that part of it was very well-documented. I didn't have any problems with it.

Don't be shy in asking questions. Google/Bing is your friend. It is complicated. There's no reason to spend eight hours trying to figure out something, except unless you are trying to learn in-depth. There are a lot of people who've done exactly what you're trying to do, and it doesn't matter what it is.

I would rate it a 10 out of 10 because it is industry standard. It did everything I could've asked. I barely scratched the surface, but what I needed it for, it did well and in a very straightforward-to-implement way.