Apache JMeter Reviews

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.

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.

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 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.

• 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.

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 are writing scripts using various tools in multiple environments. We have tests set up where you have to pass the credentials in to get a session ID, and it sets and checks the cookies. Then, we check the response values and pass them on to the next function.

We have this solution integrated with Jenkins and we also use it for database performance testing.

The most valuable features are the integration with Jenkins and the reporting.

JMeter allows us to automate performance testing and raise diagnostic functions.

This solution should support the Ruby programming language for scripting.

JMeter should support dynamic throughput so that we can reduce or increase it during the execution of the scripts. 

For performance testing, we would like to be able to select different bandwidths such as 3G or 4G.

The interface could be made more user-friendly.

I have been working with Apache JMeter for the past three months.

We have not had any problems with stability.

So far, I haven't had any issues with scalability when performance testing.

We have not yet been in contact with technical support.

I have also started working with BlazeMeter. One of the differences is that the automation is not possible in BlazeMeter. However, BlazeMeters allows for the selection of different bandwidths, it takes less time to write tests, and it is more user-friendly.

The initial setup is straightforward. We have not yet completed our full deployment with all of the tests.

Our internal team was responsible for the implementation.

We are currently comparing the differences between Apache JMeter and BlazeMeter.

JMeter is a good solution but it requires writing manual scripts and takes longer than BlazeMeter. It takes longer to cover the same number of use cases and is not as user-friendly.

I would rate this solution a four out of ten.