We performed a comparison between Apache JMeter and Eggplant Performance 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."This solution is very user-friendly, and allows for a lot of data capture when testing."
"We are using it just for load testing. We are using its free version, and it is scalable."
"We like that Apache JMeter has different features and different plugins and that they are free of charge."
"We use Apache JMeter for load testing, where we provide the throughput time."
"It is open source as well as relatively extendable. It allows us to extend and add additional functionality and features. Its deployment is also very easy."
"The reporting features are really good. There's a lot less latency than other solutions."
"I use all the tools, but one feature that stands out is JMeter's ability to test when services are sending a particular kind of request. We are using specific ports to send queries, and assess the performance based on the time it takes these queries to respond. You can use it with stuff other than the web performance."
"The most valuable feature of this solution is being able to launch many requests and scheduling simulating human interactions with the application."
"It is not a conventional test automation tool. It uses optical character recognition (OCR) to identify objects. It makes it the best in the class."
"We don't have a big team of people that can watch the dials and check that everything is okay. We're doing a lot of the monitoring of our website and our product at the side of the desk. We need a solution that does a lot for us, and that's what Eggplant does."
"We find the solution stable and scalable."
"Improving JMeter's sync time would be beneficial."
"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."
"They can improve it a little bit in terms of distribution load testing. We struggled with it during the distribution. In terms of reporting, runtime monitoring is not currently included, and it should be included. They can also improve it on the reporting side in terms of the comparison of the reports. They can also focus more on integration with CI/CD. Currently, people are using their own customized tools. It would be nice if Apache can provide some standard tools and procedures for integration with CI/CD tools like DPR. There are some tools, but it would be nice if official standard tools and procedures are available."
"They should improve the solution on its UI front."
"Automation is difficult in JMeter."
"The reports in Apache JMeter could improve."
"The reporting is not very good."
"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."
"I'd like to see the ability to integrate the user experience through device forms like AWS device forms or source labs."
"Performance is one key area for improvement. It can be slower compared to other tools I've used."
Apache JMeter is ranked 1st in Performance Testing Tools with 82 reviews while Eggplant Performance is ranked 15th in Performance Testing Tools with 4 reviews. Apache JMeter is rated 7.8, while Eggplant Performance is rated 7.8. 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 Eggplant Performance writes "Offers unique object identification, ideal for UI layer regression automation but limited scalability". Apache JMeter is most compared with BlazeMeter, Postman, Tricentis NeoLoad, Katalon Studio and OpenText LoadRunner Professional, whereas Eggplant Performance is most compared with Appium, OpenText LoadRunner Professional, Tricentis Tosca, SmartBear TestComplete and OpenText UFT One. See our Apache JMeter vs. Eggplant Performance report.
See our list of best Performance 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.