Apache JMeter Reviews

It is specifically used for performance systems. It is used for identifying the areas where we need to improve the application bottlenecks and for load testing. We are using its latest version.

It has helped us to build robust application cater to the learning domain and identify bottleneck prior go live. It helped us refine our deployment strategy and capacity planning.

It is open source as well as relatively extendable. It allows us to extend and add additional functionality and features. Its deployment is also very easy.

It should start supporting the presentation layer. It currently provides performance testing specifically at the application and API level. It can be extended to the presentation layer, which includes mainly Angular and React frameworks. 

It should also be easy to use and easy to train people.

I have been using this solution for more than ten years.

It is stable.

It is scalable. It allows us to extend and add additional functionality and features.

We have around 10 to 15 people who use this solution.

It is open source, so I don't think any support is available.

Load Runner, replaced with JMeter due to lower ROI

Its deployment is easy. It didn't take much time. It took less than 15 minutes.

We deployed it on our own.

1. Scalable Product and solutions

2. Plug and Play with CICD process

3. Reduction in licence cost 

No Licensing cost for JMeter

Yes.

I would recommend this solution. We plan to keep using this solution.

I would rate Apache JMeter a seven out of ten.

There's a third-party platform that is getting migrated to, so with the newer version migration, we were looking to see if there are any performance degradation with the migration. The product platform assures the user loads that we are planning to have on the system. Nevertheless, we wanted to have validation from a business perspective. We wanted to see that it'll still support the loads that we are looking at.

The ability to create a large number of user loads has been very helpful for us. 

It's typically straightforward to set up. 

The solution can scale well.

It's stable and reliable. 

There is lots of useful community support. 

In terms of platform support, they need to extend the support for backend platforms and more of the legacy types of platforms.

We've used the solution for a long while. We've used it for a few years. 

It's a well-trusted product. A lot of people use it. There's a lot of support in the community also. Therefore, the stability is pretty good and it is quite reliable.

We can create demand as we need. It's quite scalable. 

We have five people suing the product. The performance testers use it.

We can get a lot of support from the community. It's pretty easy to get assistance. 

We've had no issue so far when we've needed to get help. We are satisfied with the support. 

Positive

We did not previously use a different solution. 

The solution can be easy to set up depending on the target system that we are testing. However, there are situations where Apache JMeter is not supported.

The deployment took two to three weeks to set up and deploy.

We have a team of five people that can handle deployment and maintenance. 

We did the setup in-house. We have the capabilities within.

Most of the time, it's the end client who manages the license for us. We don't purchase the product by ourselves; it's the end customer who does it for us. I'm not sure what the actual cost of the product is. 

We likely are using the latest version of the solution. However, I can't be sure. I'm not sure which version number we're using. 

It's a tool that is being used by many, many others as well. There's a lot of community support out there. I'd recommend it, as long as it supports the platform.

I'd rate the solution seven out of ten. 

The tool helps us in the capacity assessment planning for our services. It helps us to make sure that the APIs will be able to afford the traffic that we expect to get from these services in the production environment. 

The product helps me get the expected performance from applications or servers and reduces costs. It also enhances the performance of the services and helped them reach their ultimate capacity. 

The tool needs to have a better Graphical User Interface. Many of the solution's features are difficult to understand due to the complex user interface and user experience. The product needs to add plugins. It should also work on the integration with external partners like IDE and API gateways. 

I have been using the solution for more than three to four years. 

The tool is stable. 

The product is scalable. My company has around four to five users for the solution. 

The product's setup is not complex. The tool's installation was very smooth.  It doesn't have any deployment process. You just need to implement a set of packages to get started with the product. 

I would rate the product an eight out of ten. 

The distributed load testing is very good and the ramp-up. When we come out with the right ramp-up plan, it can be converted into Apache JMeter script very well. This accurately simulates how many of our transactions need to be triggered.

I would like to see exceptions improved. The initial setup is complex and needs to be upgraded. It would be great to have additional protocols other than HTTP, HTTPS, and APIs.

I have been working with Apache JMeter for the past seven years.

The stability is good and I am not finding any issues.

We are not having any problems with the scalability of Apache JMeter

Technical support is very good.

Positive

The initial setup is complex.

Apache JMeter is a free tool.

I would rate Apache JMeter a nine out of ten.

We use Apache JMeter for lower-end performance testing. Sometimes we use it for Rest API testing, as well.

This solution allows us to have a detailed look at performance using different metrics. We can look at the deviation and the median values and see how it is performing. We can also analyze our servers and see how they are performing in terms of CPU and how much memory is allocated.

The most valuable feature in JMeter is the Thread Group, which helps us to see whether the performance is good.

The plugin for git allows us to scan files directly from the GitHub site.

The reporting is good and there are a lot of different formats available.

If you want to see the data that is associated with a response then you can download it in JSON format.

There is a large user community that can help you to learn and use JMeter.

When we are testing with too many threads then the solution hangs.

JMeter does not support JavaScript.

Automation is difficult in JMeter.

We have been using JMeter for the past two years.

Stability becomes an issue if we use more than 10 or 20 threads.

We have not been in contact with Apache technical support.

There is a large user community and if you need help then you can get instant help from them.

We also use Postman and when it comes to making a very large request, it is the better option. It is also a user-friendly solution and you do not have to go through a lot of documents to start using it.

JMeter works better for iterative testing.

It is easy to set up and administer JMeter.

This is an open-source product.

This is a good solution but many features would have to be added to use this tool alone. Postman has more features, so JMeter is really only good for performance testing.

I would rate this solution a seven out of ten.

We are using Apache JMeter for automation and for processing activities of our clients. Additionally, it is used for testing.

The most valuable feature of Apache JMeter is its popularity. It is the best open-source tool with all the features needed.

The reports in Apache JMeter could improve.

I have been using Apache JMeter for approximately one and a half years.

The stability of Apache JMeter is good.

Apache JMeter is scalable.

We have less than five people using this solution in my organization.

There is a lot of support available that is good, such as in forums. However, they do not have a dedicated team that you can contact.

I have not used a solution previously.

Apache JMeter was straightforward to install.

The price of Apache JMeter is good. The selling rate is quite effective and the limited users with a multi-region-related execution.

My advice to others is to go through some basic video processes, which are available on YouTube and Apache JMeter site, it has a lot of documentation that will help you get prepared and used to the tool.

I rate Apache JMeter a seven out of ten.

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.

Our use cases are for applications such as E-commerce sites where there are multiple concurrent users. In some cases, there is also API load testing where a high number API calls are required for load testing. 

Apache J meter has proved to be the tool of choice for Performance testing with various features and also it comes without any cost.

A valuable feature is that when there's a high number of TPS I can achieve more transactions per second given the hyper-limitations. If the TPS is more than 5,000 TPS, the CPUs get very high (for Load runner)  and JMeter handles that well. I'd also say that the scripting flexibility like co-relation using regular expression is good, it's in the central control. Those would be the two major valuable features. 

We have some scenarios for diameter load testing where TPS requirements are very high, 30K or 40K TPS. In the telco area, this is for simulating mobile usage. However, diameter load testing can be difficult in J Meter. The only way to imitate Diameter requests and process the responses of these requests is to implement them in the code of JSR223 samplers. JMeter generally provides synchronous calls. It's something that could maybe be improved in the future, because for achieving that very high kind of TPS, more than 30K, 40K requires a asynchronous solution. It's not a common thing, it's really very specific to the telco domain and a very few projects. 

I've been using this solution for about 18 months. 

We haven't encountered any major issues with the stability.

Scalability is good. 

Support is more open-sourced. There is a lot of material available online so we haven't had to contact Apache technical support and we have our own team in the company who maintain the product.

We sometimes use LoadRunner for various purposes but currently, we use JMeter 80% of the time because LoadRunner's CPU consumption becomes very high for TPS more than 5000. Also, LoadRunner is not free so we have to pay for the license. We're using it for very few projects now. JMeter can easily achieve a high TPS but LoadRunner has a lot of high-resource requirements. 

LoadRunner's advantage is that the output report is very comprehensive. JMeter reports are only good for the people who understand the detailed logs. Out-of-box, LoadRunner has nice reports and ease of execution. In JMeter, it's also simple but requires some online training or knowledge on the loader and the setup. 

Initial setup is quite straightforward, it takes about two hours, no more, although each project is different. It depends on the scripting that goes into the environment. In terms of the product alone, the deployment doesn't take long. If you include the hardware, it can take about a week because the hardware calls for a lot of couplers and storage units and that takes time.

For the load test which requires high transactions per second to be achieved, in the range of 15K transactions per second, this is a very good tool to use and the biggest advantage is that it is free. It has a big user group, so we can find solutions easily if there are any challenges. It's really a very good open-source tool for any organization to look at in terms of performance tests.

I would rate this solution an eight out of 10.