Apache JMeter Reviews

We use the solution for performance distributing testing.

The solution helps by detecting bottlenecks.

The solution provides a wide range of plugins and extensions, such as multiple monitors and multiple samplers. Apache JMeter can be used for multiple purposes, including performance and API testing, as well as integration testing. Additionally, users can create their own cloud and build their own distributor, eliminating the need to pay for any SaaS solution.

The UI has room for improvement.

I would like to be able to measure web performance as well using the solution. Apache JMeter is only for infrastructure testing, and backend testing, but we cannot use it for performance testing because we need to do it through the browser. 

I have been using the solution for one year.

The solution runs on Java software. 

I give the scalability a five out of ten.

The initial setup is straightforward. The documentation is very detailed.

I created a resource group in our private Azure cloud, and then I had multiple agents. This included one master and four or five slaves of Apache JMeter. I configured the Apache JMeter and began the distribution and testing.

I give the solution a seven out of ten.

I suggest using the solution and following the basics.

We're primarily using the solution for its performance. It's on our data center.

The tool has been a great help to our organization, which is focused more on quality testing as opposed to performance testing. It's provided a lot of insights. With the digital transformation that is currently happening, the need for that shift was rather critical.

The performance of the solution is excellent.

They have designed the product so that it is very easy to configure. 

You can basically do anything you like with the product. It's not very restrictive.

We like the fact that the technology is open-source.

The user interface could be improved. If they had better UI, it might make it easier to use.

You really need a technical team in order to really utilize the product.

The scalability could be better, or the process of scaling itself could be a bit more clear.

We've used the solution for a couple of years at this point.

The stability is quite good. There haven't been any issues with bugs or glitches. It doesn't crash of freeze. It's very reliable.

Nobody ever has used any tool to its full capacity, including this one. Half of the time it's how you set up and how your environment is. We can easily scale on cloud. So far, we're worried about its ability to scale. Our setup is basically a hybrid cloud where we can have private data centers and we can know exactly where each is located. However, the scaling is a big concern for me. I'm looking at BlazeMeter as well, and, although I've only really read about it, it looks like it scales quite well. With scaling, I'm sure I'll find more complexities, especially if I look into kiosk testing. I'll want to explore further test cases.

Currently, those that are on the product are mostly testing communities approaching it from a performance aspect. Every project is different and therefore the number of users goes up and down.

There isn't really a need for tech support with JMeter. There is a vibrant community, which is a good way for a lot of users or developers to go on and post a question and get an answer. The team prefers it this way. It's a positive aspect of JMeter.

I have some experience LoadRunner, however, it is expensive for what it offers. This product is open-source which makes it affordable.

The initial setup is pretty straightforward. My team was very hands-on. They didn't struggle with the UI at all and it wasn't too complex for them. That said, if a person with lesser skill levels, maybe someone who has a lower skillset, may struggle a bit with the implementation. It's geared slightly towards more technical users.

The product is an open-source solution.

I understand the Apache also has something called BlazeMeter, which is something I recently looked into.

I'm not quite sure which version of the solution our team is using right now. It's likely the latest version. We did the upgrade on our tools in 2019. It's open-source, and therefore everybody picks up the latest one.

As an open-source tool, there's a good community surrounding it. If you have automation frameworks or a DevOps pipeline, you can connect that and easily configure everything to streamline processes. Due to the fact that it's open-source, you don't have to wait to get the approvals and the budgets in order. That part alone can take months to sometimes years. If your company has the time, they should review the tools. If it seems to fit your organization, I'd recommend trying it out. 

Overall, I would rate the solution seven out of ten. It's a good open-source tool that you can configure easily, and it's very competitive in the market in terms of usability

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.

• 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 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 primarily use the solution for API testing.

The ease of use is the solution's most valuable feature. Also, the ability to easily create test cases is also very good. It's easy to just ramp up on the solution.

The solution is new to us. I'm not sure if we're using the full capabilities of the solution yet, but from what we have used, we're quite satisfied.

In future releases, it would be helpful if there was an integration with ALM Octane.

The solution is stable.

The solution is very scalable.

We're not using too many features of the solution itself, so we haven't needed the assistance of technical support yet.

We previously used LoadRunner. We decided to switch because on LoadRunner scaling up was a problem.  We needed licenses to do so and it was becoming a problem for us to simulate the number of users we were expecting. 

The general setup of the solution is straightforward.

Before we chose JMeter, we looked at NeoLoad, but it looked to have the same issues surrounding licensing that LoadRunner did.

We are using the on-premises deployment model.

The advice I would give to others would be to look at your requirements and decide if the solution is right for you. For us, it was API testing and JMeter is very good for this.

I'd rate this solution nine out of ten.