We performed a comparison between Apache JMeter and OpenText LoadRunner Cloud based on real PeerSpot user reviews.
Find out in this report how the two Performance Testing Tools solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
"It's a free tool."
"It's easy to set up."
"JMeter lets us generate virtual users and T-load, per our requirements. It's easy to configure and adjusting the virtual users according to the DPS we want to achieve."
"The solution has good transition controllers and distributed testing."
"The most valuable feature of Apache JMeter is its popularity. It is the best open-source tool with all the features needed."
"Scripting with the solution is good."
"We find the ease of use and the reports and graphs available valuable."
"It's open source, so I like that about the product. And there's a lot of community support for it."
"The usability and ability to integrate with other solutions is quite good. When I use it in on Azure, then Red Hat is the most likely solution I use. When I use AWS, then I tend to use Lambda functions. In either case, it works well and you can use it either way."
"The most valuable feature is that we do not have to accommodate the load-testing infrastructure in our own data center."
"The product supports a wide variety of technology compared to any other tool."
"The solution is easy to use."
"The fact that the solution supports multiple protocols such as open source, VuGen, TruWeb, TruClient, and SAP is very important because these protocols help us to concentrate on what is really needed to produce performance tests. If something is not supported, you have to use other tools or find other ways of assimilating loads."
"This solution is SaaS based so we can utilize cloud technology, which is less time consuming and saves a lot of of money."
"The record and playback feature is the most valuable feature. It's all driven by the script, so it's a script-based tool where the background tracing starts. Java's background process does a lot of tracing. The process starts in the background. It sees what peaks of volumes that the process can handle. It's easy to use because it's script based, record, and playback. I"
"The most valuable feature is having load generators in countries where we don’t have access to them."
"If JMeter could provide a web version of editing, that would be good."
"You really need a technical team in order to really utilize the product."
"The solution needs to improve reporting. Currently, there is not enough automation involved with the feature. For example, there should be an automatic way of saving reports."
"The UI could be better."
"Running JMeter in GUI mode uses a lot of memory, which means we need to switch to a non-GUI mode when using a heavy load."
"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."
"Automation is difficult in JMeter."
"The solution is not user-friendly, there is no framework for autocorrelation or parameterization."
"There are three modules in the system that are different products packaged into one, and they can sometimes be difficult to figure out, so they should be better integrated with each other."
"CI/CD integration could be a little bit better. When there's a test and if you see that there are high response times in the test itself, it would be great to be able to send an alert. It would give a heads-up to the architect community or ops community."
"One area of improvement in the software's support is the replaying of captured data within the development environment. It would be beneficial if the replay feature could accurately mimic what the actual application is doing for better analysis and testing."
"Sometimes, you are utilizing one of the low generators, then all of a sudden if you discontinue from one project, it actually deletes the entire low generator."
"Their documentation is not technical enough for us. We would like to have much deeper technical documentation so that we can self-serve without constantly having to go back to them and ask."
"We are trying to put it into a complete CI/CD pipeline, but there are still some challenges when you try to run it through different protocols. The challenges are around how you can containerize applications. There are some limitations to some protocols, such as desktop. And when it comes to database testing, there are some things that we can't do through CI/CD."
"Scriptless automation is an area that can be improved."
"An area for improvement is analytics on why response times are slow from certain countries."
Apache JMeter is ranked 1st in Performance Testing Tools with 82 reviews while OpenText LoadRunner Cloud is ranked 6th in Performance Testing Tools with 39 reviews. Apache JMeter is rated 7.8, while OpenText LoadRunner Cloud is rated 8.2. The top reviewer of Apache JMeter writes "It's a free tool with a vast knowledge base, but the reporting is lackluster, and it has a steep learning curve". On the other hand, the top reviewer of OpenText LoadRunner Cloud writes "Enterprise modeling, server maintenance, and competitive pricing". Apache JMeter is most compared with BlazeMeter, Postman, Tricentis NeoLoad, OpenText LoadRunner Professional and OpenText Silk Performer, whereas OpenText LoadRunner Cloud is most compared with OpenText LoadRunner Enterprise, Tricentis NeoLoad, OpenText LoadRunner Professional, BlazeMeter and OpenText UFT One. See our Apache JMeter vs. OpenText LoadRunner Cloud report.
See our list of best Performance Testing Tools vendors and best Load Testing Tools vendors.
We monitor all Performance Testing Tools reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
