#1 most frequent
United States of America
38.8%5,782 installations of 14,903
Categories & Use Cases
Product Demos
Top Performing Features
End to end performance management
Identify end to end performance bottlenecks, not just web application response time
Category average: 8.9
Integrated performance data
Cross-analysis of data gathered from all the components of the application
Category average: 9.2
Real time monitoring
Real time monitoring means monitoring the entire application environment while under load
Category average: 8.3
Areas for Improvement
Deployment model flexibility
Software can be deployed in testing lab, and also in cloud
Category average: 7.1
Automated anomaly detection
Automated anomaly detection helps detect exception conditions that can be the cause of performance degradation
Category average: 6.1
Who Buys & Uses Apache JMeter
#2 most frequent
India
13.3%1,975 installations of 14,903
#3 most frequent
United Kingdom of Great Britain and Northern Ireland
5.1%758 installations of 14,903
JMeter for performance and load testing.
Use Cases and Deployment Scope
JMeter is used predominantly for performance and load testing purposes. As our application stack is majorly microservice-based, thousands of APIs are developed, enhanced, and maintained to enable a satisfied customer experience. To achieve this, the APIs should meet the expected performance metrics, and JMeter helps in validating them through our SDLC release cycles.
Pros
- All kinds of response formats are supported.
- JMS or message based systems can also be tested seamlessly.
- Pluggable samplers, visualization tools are helpful.
- Open source and free.
Cons
- JMeter's UI or frontend can be improved to be more lightweight.
- Not ideal for user based performance testing, since no support for final rendering.
- System resource-intensive.
Return on Investment
- Positive impact in meeting the NFRs.
- Stable tool.
- Easily integrated into SDLC process pipelines.
Usability
Alternatives Considered
BlazeMeter
Other Software Used
Apache Kafka, Red Hat OpenShift, Apigee Edge, Splunk AppDynamics, Splunk Observability Cloud, Glassbox, LiSA, GitHub Copilot, GitHub, IntelliJ IDEA
Apache JMeter- the open source standard for load measuring and testing
Use Cases and Deployment Scope
Apache JMeter helps ensure our performance targets are met for release, and quantifies changes we make in the name of performance. Without it, we end up with custom code written by system testers or QA that don't always fully understand how code evolves, and then inevitably we have to throw it away in a year. Apache JMeter allows developers to run standardized performance tests ahead of QA.
Pros
- Easy to get started with
- Good, straightforward UI
- Deep options for fine tweaking under uncommon scenarios
Cons
- Some options are arcane and misleading
- Results are too easily skewed by poor methodology
Most Important Features
- Open source
- Apache license
- Broadly used
Return on Investment
- It is a almost-standard tool we use in presenting release checkpoints
- It probably saves multiple days per release of validation efforts
- It has helped developers get unstuck (perhaps saving them 2-3 days)
Alternatives Considered
Postman
Other Software Used
Froglogic Squish
World's best performance benchmarking and load testing tool
Use Cases and Deployment Scope
Apache JMeter helps our team in areas like load testing and performance benchmarking of APIs across products and services. Every new feature that gets released is the first load tested using Apahe JMeter, by passing appropriate parameters to check if it can handle the list and stress easily. This helps to assert that the service can easily serve 'x' users in 'y' conditions. With teams focusing more on microservices and agile development, non-functional testing plays a vital role. Apache JMeter is an open-source tool written in pure Java, making it the most preferable option for us to test our services, both API and UI through its user interface as well as Non-GUI mode. This makes the SDET team perform testing and feature releases more confidently with optimum quality.
Pros
- Report generation.
- Multithreading
- Log debugging and sampling.
Cons
- Optimize CPU and Memory utilization.
- Reporting visuals and metrics.
Most Important Features
- Load testing and performance KPI metrics.
- Report generation.
- Sampling and Assertions.
Return on Investment
- Frequent releases with more confidence and better quality.
- Scalability and Reliability.
- No additional costs as it's open source.
Alternatives Considered
BlazeMeter Continuous Testing Platform, Micro Focus LoadRunner (formerly HP LoadRunner) and k6 (formerly Load Impact)
Other Software Used
BlazeMeter Continuous Testing Platform, Micro Focus LoadRunner (formerly HP LoadRunner), k6 (formerly Load Impact)
Performance is a key and JMeter is a solution
Pros
- Jmeter is an open source and highly customized tool for your needs. There are open source JMeter plugins also available in the market to extend JMeter existing functionality.
- JMeter provides a very easy user interface and pluggable components, and different visual charts and summary report listeners. Also nowadays JMeter supports quite rich HTML reporting.
- JMeter can be used for volume testing, load testing, availability testing. Also, it allows the master and slave concept. Hence you can create multiple load generators and controllers, and JMeter will give you combined execution status.
- JMeter provides great documentation.
Cons
- To get a summarized HTML report, the user needs to configure a lot of things. It should be done with a single click like other paid tools in the market.
- Support to measure desktop based application performance.
Return on Investment
- 100% ROI with more customized JMeter framework.
- We have fine-tuned a lot of performance issues related to our application using JMeter.
- The only negative ROI is you need highly skilled people who know coding for creating dynamic JMeter scripts.
Alternatives Considered
Micro Focus LoadRunner (formerly HP LoadRunner) and Microsoft Visual Studio Team System
Other Software Used
Atlassian Confluence, JIRA Software, SQL Developer
Best tool for performance testing
Use Cases and Deployment Scope
Jmeter is used for the load or performance testing of an application. It is used to identify the bottleneck in the performance and improve the user experience. We have used for newly created authenticated API, Identify management system, and database to store PII. It is worth the tool to create your project and scripts to benchmark the performance numbers for future releases and improvements. We have found many bottlenecks in the application which required to re-design the data flow with the help of Jmeter.
Pros
- Performance Testing.
- Load Testing.
- Penetration Testing.
- Scale the test and rerun existing scripts.
Cons
- Project Creation.
- Variable declaration.
- Global Design UI.
- End User scenario to execute like live users performing the action on the application.
Most Important Features
- Creating Scripts.
- Running Scripts.
- Generate Report.
- End User test scenario.
- Authentication, Http Header, Request and Response.
Return on Investment
- Good ROI on improving the performance of the application.
- Finding issues in the performance.
- Benchmark the performance results.
- CON: Need skillset to create and maintain the scripts in Java.
- Scripts are reusable and it is executed by any user.
- Need Client and Server setup to execute the scripts.
Alternatives Considered
Micro Focus LoadRunner (formerly HP LoadRunner)
Other Software Used
LambdaTest, Slack, Microsoft Teams