Apache JMeter Reviews

We normally use it for testing APIs or scenarios where the user load is very low. We use JMeter for performing online UI performance test execution, particularly for conditions involving only HTTP or HTTPS protocols. 

It's employed predominantly for executing tests on hundreds to a few hundred users. We also use JMeter in our CI/CD integration suite, where it automatically triggers tests when a new build is generated.

JMeter can be integrated with most open-source platforms like Grafana, Prometheus, or even with custom-made tools by extending it and integrating from GitHub. It supports generating comprehensive reports with numerous listeners. 

Although we don't utilize all the listeners, JMeter provides diverse reporting capabilities that we can leverage. Furthermore, JMeter facilitates scripting capabilities, which include options for Groovy scripts.

The primary use case for Apache JMeter is performance testing. We use it to test the performance of applications.

Apache JMeter offers plugins for reporting and preparing test scenarios. It allows recording to customization, letting you download plugins to connect with databases or external systems. Despite being open source, it offers features comparable to paid tools, and its ability to customize and expand is particularly useful. Additionally, its open-source nature makes it cost-effective.

I worked on the performance setting of my product, which is a product with an easy UI element that can be added in. People without forward knowledge will be able to easily understand the tool and use it right away.

Other cloud-based performance tools will allow you to view what's going on during the test. However, with this product, it's not possible to monitor live during a test, such as with BlazeMeter, which is very user-friendly.

We are using JMeter for load testing and UI performance testing in both GUI and non-GUI modes. We mainly use it for performance testing and rendering purposes across various projects.

With JMeter, we can execute load tests and generate reports quickly in our CI/CD pipeline, immediately identifying and resolving server and client-side issues before deployment. It effectively scales our testing capabilities without incurring additional costs for increased load.

We have multiple use cases. We have APIs integrated for functionality. We're using JMeter for performance testing those APIs.

There are about 80 people working on this project, and about 12 people are using JMeter for performance testing.

Approximately 10% of people are using JMeter in my organization, and some people are using PureLoad, which is a paid tool.

We're using version 4. The solution is deployed on an Azure public cloud.

The reporting features are really good. There's a lot less latency than other solutions. We configure our API script and execute it through JMeter, get a response time over there, and compare that response time with the Azure cloud response time. The latency is low. JMeter is optimized very well. 

Another valuable feature is that we can distribute our load in different formats, like a responsive load. Then, we can distribute our load in a different manner by using plugins.

We decided to use JMeter because it's open source, and it's a very stable product. There are many plugins that are easily available to configure multiple things.

I mainly used Apache JMeter for manufacturing environments at an enterprise level. One specific use case was where we had to send bulk files via API, which we could not replicate with LoadRunner as it might require additional protocol purchases. With Apache JMeter, we could simulate this scenario, uploading millions of files via API.

There is no significant financial investment as Apache JMeter is a free tool, which helps in scenarios where cost constraints are present.

JMeter is used by a team of four performance engineers. We monitor tasks on the API level, so all of the requests are hitting individually.

JMeter has helped us streamline our applications by identifying multiple bottlenecks in our systems and exercising tasks against APIs.

We use this solution mostly for creating scripts, load testing, and performance testing. If my client doesn't have a tool or I don't have a tool, I try to leverage JMeter because it's an open-source tool.

I personally use JMeter for things which cannot be covered by our load testing tool, which is OATS, Oracle Application Testing Suite. This is a tool that was developed by Oracle but is no longer in use because Oracle has stopped developing it.

The solution is deployed on-prem and on private and public clouds.

JMeter should be more stable. Every time there is a new release coming up, a lot of its older functionalities or the new functionalities that are brought in are not very well-documented. It should be documented properly, and there should be proper use cases. A lot of the newer features don't work, and sometimes you have to spend a lot of time maintaining the scripts. That is something JMeter could probably look at.

For example, in JMeter 5 they brought in a lot of new controllers. But there isn't a lot of documentation available on the Apache site on how you're supposed to use those controllers. They've explained the controller functionality, but there aren't any proper use cases to show that.