Jmeter- Performance testing tool
Updated February 25, 2015

Jmeter- Performance testing tool

Ameeta Muralidharan | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Review Source

Software Version


Modules Used

  • Thread Group, transaction controller to test Java web applications
  • used almost all the elements

Overall Satisfaction with JMeter

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

Using JMeter

It is good to use. I still use it in my current job location to do performance testing of web applications