We performed a comparison between Apache JMeter and RadView WebLOAD 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."When there's a high number of TPS I can achieve more transactions per seconds given the hyper-limitations."
"The most valuable feature of this solution is being able to launch many requests and scheduling simulating human interactions with the application."
"It is very quick and user-friendly."
"JMeter is user-friendly, and that's a notable advantage of JVTech. It's straightforward and easy to use, unlike some other load testing tools, making it very easy to understand."
"The distributed load testing is very good with Apache JMeter."
"We are using it just for load testing. We are using its free version, and it is scalable."
"The solution is scalable."
"The biggest thing I liked about it is that there is a huge user base out there, and being shareware and being Apache, if I have any question on how to get something done, I get 18 different answers. Out of those, there would be at least a few good approaches for what I was trying to do. So, the support system out there is most valuable."
"The solution is simple and useful."
"The most valuable feature of this solution is reporting."
"The most valuable aspect is that the IDE is simple and it's quick to complete the process."
"What needs improvement in Apache JMeter is the very high load requirements when you want to scale it beyond certain thresholds. For example, small to mid-range testing is very easily done with Apache JMeter, but if you scale and increase the load, then it would be a problem because the tool consumes a lot of resources, probably because Apache JMeter provides an enriched UI experience, so it consumes a lot of memory and requires high CPU usage. This means you have to manage your infrastructure, or else you'll have high overhead expenses. As Apache JMeter is a heavyweight tool, that is an area for improvement, though I'm unsure if Apache can do something about it because it could be a result of the way it's architected. What I'd like to see from Apache JMeter in the future is for it to transition to the cloud, as a lot of cloud technologies emerge around the globe, and a lot of people prefer cloud-based solutions or cloud-native tools. Even if a company has a legacy system, it's still possible to transition to the cloud. I've worked with a company that was an on-premise company that moved to the cloud and became cloud-native. If Apache JMeter could transition to the cloud, similar to k6, then it could help lessen the intense resource consumption that's currently happening in Apache JMeter."
"If the solution was GUI based, I believe that it would be more versatile."
"In terms of setup, it could be nicer, to be honest. Sometimes, I get a little bit lost."
"The solution's setup could be easier and security could be improved to minimize vulnerabilities."
"I sometimes found the documentation to be not as explanatory as I would've liked it. In the cases that I can think of, I was looking for a rather hand-holding approach with Step A, B, and C, but then I realized that with a product that is open source like this, you can't do handholding. That is because there are so many different uses and different unique environments and setups for it, but I remember thinking a few times that if they only just said this."
"Modeling a test is difficult. If you don't have much knowledge, you won't be able to do it easily. Testing APIs is also difficult."
"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."
"Improving JMeter's sync time would be beneficial."
"There is no analytical dashboard."
"The reporting side of things is really complicated. It's difficult to get out exactly what you're looking for, there are almost too many options."
"Technical support is slow and wastes a lot of time, so it needs to be improved."
Apache JMeter is ranked 1st in Performance Testing Tools with 82 reviews while RadView WebLOAD is ranked 11th in Performance Testing Tools with 9 reviews. Apache JMeter is rated 7.8, while RadView WebLOAD 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 RadView WebLOAD writes "IDE is simple and it's quick to complete the process but the reporting is complicated". Apache JMeter is most compared with BlazeMeter, Postman, Tricentis NeoLoad, Katalon Studio and OpenText LoadRunner Professional, whereas RadView WebLOAD is most compared with Tricentis NeoLoad, OpenText LoadRunner Professional, BlazeMeter and k6 Open Source. See our Apache JMeter vs. RadView WebLOAD 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.