Skip to main content
TrustRadius
JMeter

JMeter

Overview

What is JMeter?

JMeter, from Apache, is a load and performance testing tool.

Read more
Recent Reviews

TrustRadius Insights

JMeter has become a go-to tool for organizations across various industries, offering a range of use cases. Users have found JMeter to be …
Continue reading

Flexible load testing

8 out of 10
July 28, 2021
Incentivized
We used JMeter for performance and load testing of our cloud service to verify that it worked well with many users before launch and also …
Continue reading

JMeter Review

6 out of 10
October 11, 2017
Incentivized
We used this product to do graphing and on the fly reporting. It allows us to pull data and graph it without laying it out carefully every …
Continue reading
Read all reviews

Popular Features

View all 5 features
  • End to end performance management (21)
    9.0
    90%
  • Real time monitoring (21)
    8.8
    88%
  • Integrated performance data (22)
    8.7
    87%
  • Deployment model flexibility (21)
    6.7
    67%
Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is JMeter?

JMeter, from Apache, is a load and performance testing tool.

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

89 people also want pricing

Alternatives Pricing

What is Tricentis NeoLoad?

Tricentis NeoLoad is a solution for continuous performance testing software to automate API and application load testing. It was developed by the French company Neotys and acquired by Tricentis, along with the company, in March 2021.

Return to navigation

Product Demos

Apache JMeter - GUI Mode | How to open JMeter in GUI mode?

YouTube

Mobile Performance Testing using LoadRunner and JMeter (Demo Session 1) - By Isha Training Solutions

YouTube

How To Make 100000 Request Spring REST API | Apache JMeter Demo | Performance Testing | InterviewDOT

YouTube
Return to navigation

Features

Load Testing

Load testing is the simplest form of performance testing and is designed to test system behavior under expected loads

7.6
Avg 8.4
Return to navigation

Product Details

JMeter Integrations

JMeter Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo

Frequently Asked Questions

JMeter, from Apache, is a load and performance testing tool.

Reviewers rate End to end performance management highest, with a score of 9.

The most common users of JMeter are from Enterprises (1,001+ employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(143)

Community Insights

TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!

JMeter has become a go-to tool for organizations across various industries, offering a range of use cases. Users have found JMeter to be versatile in addressing different testing needs, including unit testing, functional testing, performance testing, load testing, and stress testing. With its ability to identify memory leaks, database connection issues, and virtual server problems, JMeter has proven invaluable in troubleshooting and optimization efforts.

The tool has played a crucial role in performance and load testing, allowing users to thoroughly review test cases and use cases. By leveraging JMeter's capabilities, users have been able to pinpoint shortcomings in virtual server setups and uncover web service breakdowns. Many organizations rely on JMeter annually before holiday peaks to assess site and system performance, fix any issues that may arise, and detect regressions in performance.

JMeter's popularity as a load testing tool stems from its ease of use, cost-saving benefits as an open-source tool, and overall usefulness. Users take advantage of JMeter's capability to generate HTTP requests for simulating browser activity and making back-end REST API calls. It has also been instrumental in testing Java web applications and analyzing response time and throughput.

Moreover, JMeter helps estimate application sustainability under high load and determine resource requirements based on specific client needs. Users depend on JMeter to build load profiles, measure web application response times accurately, and monitor system performance effectively.

In the banking and finance sector specifically, JMeter finds extensive usage for performance testing to ensure rich transaction performance. It assists in identifying bottlenecks and simulating different user loads to test web applications under various patterns. Additionally, organizations also rely on JMeter to execute performance tests on web services and assure that any changes made do not adversely affect their overall performance.

As cloud-based applications gain prominence, JMeter is emerging as the standard tool for testing such applications within organizations. Its open-source nature, ease of use, and cost-effectiveness make it a preferred choice, replacing legacy tools like Silk Performer. JMeter is frequently employed to test the functionality and performance of web APIs, assess website performance, and conduct load and stress testing.

The versatility of JMeter extends beyond web applications; it is widely used to test the scalability, reliability, and responsiveness of both mobile and desktop applications. Users have successfully utilized JMeter to address response time issues and improve overall performance metrics for client products.

Overall, organizations are increasingly adopting JMeter due to its ease of use, cost-saving benefits as an open-source tool, and its ability to construct tests quickly. The tool has gained popularity in organizations across various domains, including banking, finance, e-commerce, and software development.

One of the key use cases for JMeter is load testing restful web services. Users rely on JMeter to diagnose issues like memory leaks and ensure that these services can handle high user loads and stress conditions. JMeter's capability to simulate different user loads allows organizations to test web applications under various scenarios and identify potential bottlenecks. In addition, JMeter is widely used for performance benchmarking of APIs to determine their ability to handle heavy loads and maintain optimal performance.

Another significant use case for JMeter is in the testing of cloud-based applications. With the growing trend of cloud computing, organizations need a reliable tool to assess the performance and scalability of their cloud-based applications. JMeter's ease of use, cost-effectiveness, and ability to simulate real-world scenarios make it an ideal choice for testing cloud applications.

JMeter also plays a crucial role in evaluating the functionality and performance of web APIs. Users leverage its capabilities to send HTTP requests, measure response times, analyze throughput, and identify any potential issues with API endpoints. This enables organizations to ensure that their APIs are performing optimally and meeting the needs of their users.

Moreover, JMeter is widely used for assessing website performance by measuring response times under different load conditions. This allows organizations to identify potential performance bottlenecks in their websites and optimize them for better user experience.

Overall, JMeter offers a wide range of use cases and has become a go-to tool for organizations looking to test the performance, scalability, and reliability of their web applications, APIs, and cloud-based systems. Its versatility, ease of use, and cost-saving benefits make it a popular choice among developers and testers alike.

User-Friendly Interface: Many users have praised JMeter for its user-friendly interface, stating that it makes load testing and stress testing efficient and easy. They appreciate the clear documentation provided by JMeter, which helps them test their applications' performance and resolve any issues before going into production. The friendly and easy-to-use UI of JMeter contributes to its popularity among testers.

Powerful Load Testing Functionality: Users consider JMeter a powerful tool for analyzing product performance through load testing. They find it very useful for performing performance tests in a detailed manner and consider it more complete than other tools like NeoLoad and LoadRunner. The ability to automate JMeter tests and integrate them with Jenkins is seen as a major advantage by users. The availability of various testing features, including functional and automation testing, is also appreciated.

Flexibility and Customization: Users highlight the flexibility of JMeter, allowing for customization according to their specific needs. They value the ability to replicate real-time scenarios, efficiently manage cookies, and utilize thread groups. Additionally, they highly appreciate the abundance of information available on the web about building custom flows with JMeter. The flexibility of JMeter along with the availability of numerous plugins are highlighted as valuable features by users.

Poor reporting feature: Some users have mentioned that they are not satisfied with the reporting feature in JMeter. They feel that it is lacking in terms of providing comprehensive test results and could be improved to offer more insightful data analysis.

Inefficient resource utilization: Several reviewers have stated that JMeter does not efficiently utilize system resources. This means that when simulating loads, JMeter requires a larger number of instances compared to other tools performing similar tasks. Users believe that optimizing resource usage would enhance performance and scalability.

Difficult script management: Users have expressed frustration with managing scripts in JMeter. The .jmx file format used for scripts is considered difficult to work with as it is not written as code, making it challenging to compare different versions or edit recorded test scenarios without re-recording them from scratch. Simplifying script management would greatly improve user experience and productivity.

Users commonly recommend JMeter for the following purposes: API Call Validation and Load Testing. JMeter has proven effective in testing critical applications and ensuring their performance before going live. It is highly compatible, adaptable, and open source, which allows users to easily integrate it into their existing infrastructure. JMeter is recommended for performance testing, including load testing, software testing, and test automation. It is particularly useful for load testing web applications with numerous users and conducting stress tests. Users advise against running CPU extensive applications with JMeter and emphasize the importance of taking the time to properly learn the tool in order to maximize its potential and effectively solve problems.

Attribute Ratings

Reviews

(1-3 of 3)
Companies can't remove reviews or game the system. Here's why
Artavazd Yeritsyan | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
We used JMeter as a tool for performance testing of our web application for both frontend/backend. We have configured jobs on Jenkins to execute jmeter tests on parallel. For ex. we have tried out registration performance both on Stage and Live environments in parallel with the same parameters to compare the results.
  • Apache JMeter is a great tool for doing performance testing of web-applications.
  • Apache JMeter also can be used for functional tests because it has a set of assertions and extractors (i.e. elements) which allow you to not only get the page from the server, but also to control its content. In this mode, JMeter saves much more information about each request (full response and request body).
  • To make browser emulation more realistic, JMeter has elements which can work with cookies and cache. These elements are HTTP Cookie Manager and HTTP Cache Manager.
  • JMeter uses a synchronous request approach. That means for every request JMeter generates, an internal thread is raised and therefore blocked until a response is being received or a timeout happens. This results in resource blocking on the load injector. The maximum number of threads is limited within a JVM - dependent on the underlying infrastructure - and even if you are able to run a lot of parallel threads this will result in a higher CPU and memory utilization. Although performance tweaking and scaling out to distributed testing might help in such a case, it makes testing more complex and error-prone.
  • This behavior can result in distorted metrics. Think about a typical breakpoint load test. You want to determine, which is the maximum number of requests per second your tested system can serve. This will be limited by JMeter to max_requests_per_second = (1000 / average_request_time_in milliseconds) * max_jmeter_threads.
  • Even if the system could serve more, this is the maximum number JMeter can inject. This is especially important when the tested application has long response cycles, e.g. because of long lasting transactions or long lasting calculations within the requests.
If you want calculate request and response time JMeter will be very valuable for you, but if you want to do Stress Testing with thousands of simulated users, it will be not very valuable.
  • It has only postiive impact.
  • Gomez
Gomez doesn't have problems like the waiting time for a test to run, a limited number of locations and browser agents, lack of reports, etc. But Gomez is a commercial software and JMeter is not.
1
We have started to use another tool (Gomez)
Ameeta Muralidharan | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Jmeter was used by my organization to test Java web applications. We used to prepare scripts based on the use case scenario which was performed frequently. We used to then perform load, soak tests using these scripts to analyse response time, throughput of the web application. We also used to monitor system performance like CPU, memory performance during these tests.
It is used by my department. It handles the business problems of estimating how much the application would sustain under high load, resources required for a particular client requirement.
  • Jmeter scripts are good to be used for load and soak tests. This helps in analysing response times and throughput. For example for a particular application it would give response time for each transaction you perform like login, submitting information etc.
  • Jmeter has elements like listeners which helps us visualize results and helps us compare them. This helps in analyzing the results faster. For example to compare response times of different transactions
  • Jmeter is flexible and can be used to test any applications apart from Java. For example I tried to prepare scripts for SOAP and web service.
  • Jmeter requires many tweaks with respect to its configuration file and thread properties. users need to edit theses files themselves. There could be some interface where we can edit this fields.
  • Jmeter cannot handle more threads and hangs up when we increase the number of threads. This causes lot of inconvenience. In these situations, user can be notified that such change would be lead to slow performance so that user can do as required. The same appears when we try to view huge files on graph listener.
  • Jmeter should optimize the read and write access to output csv since it acts as overhead to the I/O performance. This affects our test results for the application which we are testing.
It is well suited for beginners. Users need to do the parametrization and correlation all by themselves to prepare scripts. So they can understand how do performance testing tools work. It works well for testing web applications or to identify any bottleneck or root cause of a failure. For example I faced a concurrency issue where when two reports were generated at the same time. It would generate two 0kb pdf files with no content. Jmeter helped me in resolving this issue. It is not well suited for functional testing since other tools like selenium or imacro would be better since they require less of parameterization and correlation.
  • It helped to estimate resources required for a particular client requirement. For example if the client wants the application to be used by 500 users for 1 hour, based on the load test we perform for 500 users and 1 hour we recommend resources and their capabilities.
  • Jmeter was used to identify bottleneck. This would lead to better performance.
  • Jmeter was used to identify failures as well.
  • load runner
Load runner is better to use and quicker than Jmeter. Jmeter is open source software but Load runner is licensed.
2
It is good to use. I still use it in my current job location to do performance testing of web applications
Score 9 out of 10
Vetted Review
Verified User
We use JMeter to load test restful web services. It was a little tough to get the initial setup done, but once you are past that hump, it becomes much easier to use. We were able to use JMeter to diagnose a memory leak and prove to management that we had resolved the issue, and not just making a wild shoot in the dark. Now that we have all of our basic uploads setup and configured, it only take 10-15 minutes to set up for a new test. We haven't had as good of luck with using this to load test HTML webpages, but we are still working through those issues. Overall, we are pleased with JMeter.
  • Restful web service load tests - some what complex to setup, but easy to use once it is.
  • More real world examples to help with learning the product
  • Easier setup to load test HTML pages
  • Not particularly suited for Functional testing
For a free product, it performs wonderfully with load testing, with a relatively lightweight application and easy re-use makes for a winning combo. I would definitely recommend this to anyone looking for a load test application.
  • Faster resolution of issue that only occur when the servers are under load
  • ROI is great as JMeter does not cost
It's awesome at a cost of $0
5
Quality Assurance Engineers, Programmers, and Systems Engineers
5
QA Engineers are the ones that use JMeter the most, but support from a programmer (to provide what the servers need as parameters) and a Systems engineer (to monitor the servers and provide feedback on load tests)
  • Load test Restful web services
  • Load test SOAP requests
  • Load test HTML pages
Return to navigation