Apache JMeter Reviews

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.

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. 

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.

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.

Our primary use for it is testing websites: load testing and performance testing.

JMeter is very easy for a user who doesn't have too much programming knowledge, as scripting is not mandatory nor essential to create the testing scenarios. This means the user doesn't need to know how to write code to run a complete set of load tests. Although, If you're an advanced user, JMeter does gives the possibility of using BeanShell, Groovy or Java to script your tests.

JMeter has a very friendly and intuitive User Interface which allows users to configure the scenarios reusing components already defined, which you can also modify to fit the requirements of the tests.

One very important feature of JMeter is that it is open source and it can be easily extended through a huge set of available plugins.

Considering the kinds of tests we are performing here, where we launch several tests at the same time as a batch request, JMeter is not the best tool for the job. Those kinds of things could be done easily with other tools, like k6. It would be simpler that way. JMeter is a very old tool. It has been around for about 15 years. While it has been improved over the last few years, it is a little complicated to run several tests at the same time with different sites.

JMeter could be easier. It would be a great improvement if it was easier to integrate with the CI deployments, with tools like Jenkins or CircleCI.

Our teams have been using it for about five years.

It is a very stable tool.

In my opinion, it is not scalable. We haven't found an easy way to do that.

We would like to increase our usage but we are trying to figure out the best way to integrate it with our new circuit. Our plan is to use a tool like this with customers. That is the reason we are evaluating the pros and cons of different tools. We want to incorporate these tools into our web development process, mainly in our CI/CD process. We are trying to figure out how to use tools that are designed to empower developers.

We have used LoadUI and SmartBear with tools like Selenium. Some of the developers, at that time, were used to JMeter and they introduced it. It is a very nice tool.

The initial setup is simple. It is not a hard tool to use. It has a very nice UI and the end-users are very comfortable using the tool. People deploy it themselves.

I would definitely recommend JMeter. It is a very nice tool. It is easy to use and there are several components already developed in the tool that you can use to simplify the process of defining and redefining scripts. But I would like it to be more flexible and integrate with other tools.

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.

• Recording/Playback
• Templates for test plans (NEW)
• Integrate with Java and many other scripting languages
• Integrating with external plug-ins

• The recording feature makes it easy to create test plans
• They have templates that make starting very easy (this feature is added recently)
• Supports a lot of protocols (HTTP, HTTPS, FTP , SMTP etc)
• Simplicity of use
• As compared to commercial tools, it provides better reporting features through third-party plug-ins
• There's also a huge community around tool, and because of that when there's an issue, you can get solutions easily, and without cost For example, we dis a very complex testing of HL7 protocols, which JMeter doesn't support directly, but it's extendable to support the protocols
• Supports Java and other scripting languages and can extend capabilities.

Reporting could be better if it could be like commercial tools. For example, a nice chart and visualizations. You can’t rely on the first 100 test results because the ramp-up and ramp-down time gives false results with outliers. It would be great if an option to ignore first 100 and last 100 records from results and then generate reports, should be great. Needs to support more concurrent users by single JMeter instance (agent/slave)

I've been using it for over last five years, and it is a major, active open source tool.

No issues with recent releases

There are issues when tests are stopped with large number of concurrent users. Test is not stopped as expected.

There is a huge community around JMeter. Hence free support is available to the users.

Excellent (from the community)

Grinder. Grinder was not user friendly and had to do lot of coding and low level configurations. It was lighter than JMeter.

Initial setup is straight forward. You need to have have JDK or JRE for running JMeter.

We have a team of testers capable of managing the JMeter perfromance testing project effectively.

It's easy to use and free, a huge community, and it offers a risk free to start, so use it for application performance testing. It supports connectivies with databases, FTP, and other system protocols.