Apache JMeter Reviews

The solution is primarily used for load testing.

When someone in our organization wants to test web applications, they use Apache JMeter since they face no hurdles while using the solution. Also, we can even increase the number of users using it.

All the features mentioned under JMeter metrics are available to use. Feature-wise, the solution has everything in it that I want.

Self-healing and page rendering for the end-users are not available in Apache JMeter. Hence, these are the two areas that need to be made available in future releases of the solution.

I have been using Apache JMeter for eight years. Also, I am using the solution's latest version, and any of the solution's versions support all the applications in my organization. Our company is an end-user of the solution.

Stability-wise, I rate the solution a seven out of ten.

There are around 50,000 users in my company using the solution. Also, most of the users are involved in performance testing. Scalability-wise, I rate the solution a seven out of ten.

With Apache JMeter, banking processes may face some scalability issues.

There is no support at all for the solution. Basically, it provides zero support.

The solution's initial setup process was straightforward since one only needs to download Apache JMeter and use it after that. Basically, there is no need to do any installation.

There is no need for any maintenance in the solution since it is an open-source product.

Since it is an open-source product, buying or paying for any license is unnecessary. One just needs to download it to be able to use it.

I would recommend the product to those planning to use it as an open-source product, and there is no need to buy a license. So, it is free of cost application. However, I am not sure about the product from a security perspective. But nowadays, banking people are also using it, but it won't be scalable in a banking environment where a large number of people want to use it. Using the solution, one can only test web applications and not use the tool for page rendering. I rate the overall solution a seven out of ten.

I use the solution for performance testing (Load testing, Volume testing and Endurance testing).

The solution has a friendly user interface and is a very good open-source solution for load testing. It supports both web and mobile network recording via proxy and offers a wide range of protocols. It has strong community support across multiple platforms.

The solution is open-source. 

It is very easy to code and develop the script and it supports web and mobile scripting.

There is a lot of good documentation available. 

The solution is stable. 

The memory utilization in JMeter is poor. Limited in terms of scalability. The system gets hung up for complex scripts and heavy loads which requires improvement.

It needs improvement in analytics and statistics reporting. The reports offer limited information on a load test. I would highly appreciate it if JMeter can provide better reporting capabilities.

I have been using this solution for two years.

It's a stable and reliable product. There are no major bugs or glitches and doesn't crash. 

The solution is scalable. However, it has a lot of memory issues during scale-up. That is the one concern. It's a bit limited in terms of scalability.

I have never contacted Apache customer service for any issues. However, the documentation is readily available online and very useful.

The initial setup is pretty straightforward and easy to implement. It's not overly complex. 

I'd rate it a five out of five in terms of ease of implementation. 

I can do the implementation by myself.

It is an open-source tool.

I'd rate the solution eight out of ten.

We mainly use this product for load and endurance testing.

This solution is very user-friendly, and allows for a lot of data capture when testing.  

We also found that the test scripts that the system automatically generates are extremely well created.

We would like more documentation to be provided for the advanced level features that are available in this solution, in order to improve development.

We have been using this solution for two to three years.

We have found this solution to be very stable overall.

We believe this to be a scalable solution, although we have not made any amendments in user numbers to date.

The initial setup of this solution was very simple; the product is open-source, so only requires a download in order for the implementation to be executed.

We implemented this solution using our in-house team.

This is an open-source solution, so there is no requirement for licenses.

We would recommend that any organization using this solution for test script development, may also want to look for a complementary product to handle script exhibition.

I would rate this solution a seven out of ten.

We use it to measure the performance of the system and for balancing.

We like that Apache JMeter has different features and different plugins and that they are free of charge.

We also like that lots of people use it. So, if we happen to get stuck at some point, then we can search for solutions on Google and find them.

Report generation needs to be improved. It is quite difficult to get to.

We've been using Apache JMeter for two years.

It is quite stable.

It is a scalable solution.

On a scale from one to ten, I would rate Apache JMeter at nine. I would recommend it for medium-sized businesses.

In Micro Focus LoadRunner we can go from the UI and we can configure it. There is no such feature in Apache JMeter. There should be UI-based recording history or logs.

I have been using Apache JMeter for one year.

Apache JMeter is stable.

I have found Apache JMeter to be scalable.

Since Apache JMeter is open source there is no vendor support, you have to use the online communities available.

I have used Micro Focus LoadRunner previously and it is better features than Apache JMeter. However, it is not free.

The initial setup was easy for Apache JMeter.

Apache JMeter is a free open source solution and it is why we are using it.

For those who do not want to spend money on tools then this solution would be a good choice. This is the best solution in the open-source category.

I rate Apache JMeter an eight out of ten.

We are using it for load testing. We test other companies' programs.

We are using it just for load testing. We are using its free version, and it is scalable.

I am not satisfied with this solution. Its UI side is not so easy to use for beginners. It should be easier. 

Modeling a test is difficult. If you don't have much knowledge, you won't be able to do it easily. Testing APIs is also difficult.

For JSON, you can use tools such as JSONBuddy, but they are difficult to get in JMeter. It should be easy to get JSONBuddy from the website. I have to use BlazeMeter only to get JSONBuddy.

It has been about five months.

It is not so stable.

It is scalable.

Their support is fine. There are not many Apache documents, but you can find other documents on the web.

It is not so difficult.

We are using the free version.

I would rate it a seven out of 10.

I implement this solution for my clients.

It is very quick and user-friendly.

If the solution was GUI based, I believe that it would be more versatile.

I have been using this solution anywhere from six to eight years.

The solution is stable, I would definitely recommend it to those who are considering it.

The solution is scalable.

No licensing is required as it is a free, open-source tool.

We primarily use the solution for testing. We have three types of testing. One is the APA testing, and the web, and one is mobile. All have been recorded through this protocol.

We appreciate that the solution is free to use, as an open-source tool.

We're using all of the lightweight technology with the AngularJS and Springboard applications, all the EPAs only. We use these CTP samples for all the web, as well as the EPAs. 

The initial setup is pretty straightforward.

The product is easier to learn than paid tools. You can find training online on YouTube, or you can Google it to find out more about the solution and how to use it.

The JMeter community has developed a lot of IoT protocols. 

We're like the solution to be more user-friendly. 

As freeware, not everything is readily available. You can't play around with everything. That's just due to the fact that it's not a paid tool. When you pay for tools, you get a bit more. 

Not everything is supported by JMeter. It's limited.

With JMeter, with banking encryption, we have struggled a lot. It's not as good as other paid tools that provide support and configuration capabilities that JMeter lacks. 

The solution doesn't really have good documentation, and, if you run into issues you can't simply raise a ticket. There's no help available to you.

There are certain protocols that you can get on other solutions, such as LoadRunner, that you can't get on JMeter.

The stability is pretty good. You can execute any kind of tech with JMeter as well. It's an open-source community. There are a number of samples are available. You can achieve it in different ways, however, the stability is quite good. That said, we have experienced glitches. 

Scalability is possible. You need to have the load generator for the scaling of your application. It's very simple to procure the load generator. You will have to install the JMeter agent file, where it'll be connecting to the monitor. It will not be as simple as a paid tool. For example, with BlazeMeter, they provide scaling with the cloud. BlazeMeter supports the JMeter items. If you have thousands of users, you will need the cloud and you'll need something like BlazeMeter. 

Currently, as this is a banking application, we don't have that many users. However, I've tried it with the 5000 users with the five to six load generators in the cloud. If we want to really scale, however, it's best to go with BlazeMeter.

As an open-source tool, support is not available for JMeter.

We also use NeoLoad. JMeter is open-source. It suggests you need to install that and you can make the cloud as a distributor system. NeoLoad is paid. We have some licenses and discounts. We cannot use NeoLoad due to the licenses. That's why we moved the solution to JMeter which is free and open-source.

The initial implementation is very simple. Initially, when setting up JMeter, you have to follow the proper documentation. It's very simple, however, if you do make some mistakes, you'll not be able to set up the distributed system. You need to have a little bit of networking knowledge so that all the systems should be in the same network and subnet. Connectivity should be established. It can be very difficult to execute. If you try to do everything all at once. I had some experience and I did it in the parts. It's very simple for me.

I handled the implementation myself. 

The solution is open-source and free to use.

So long as you don't have to scale too much, it's very cost-effective. If you do have to scale your users, it's best to move over to BlazeMeter, which is reasonably priced, user-friendly, and works well.

I would not recommend this solution for machine-critical applications such as banking or telecom applications. For those, we would go for paid tools. That way, if there are any technical issues or technical breaches with the tool, with the application we are supporting, we can call on support for troubleshooting. With JMeter, we don't have this option. It is good, however, for non-critical applications. In telecom or banking applications, they need to have critical releases and patches, and issues have a high likelihood of leading to a loss of business. We don't want to take chances. However, for non-critical items, JMeter is fine.

I'd recommend the solution to other users so long as they keep in mind JMeter's capabilities are limited. The upside is it is free to use, however, there's also a limit, to some extent, on how you can use it. IF you have a small-scale organization and a small number of users, JMeter will work well.

I'd rate the solution at a seven out of ten.