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."We find the load testing feature valuable."
"We are using it just for load testing. We are using its free version, and it is scalable."
"Apache JMeter is well-known and widely used among developers, particularly on popular developer forums. While it may not have the most user-friendly interface, it offers strong support through official manuals and various articles from companies providing load testing services. The tool is free, has a substantial community, and serves as a fundamental choice for testers, especially those new to performance testing. While other tools like K6 may be more developer-oriented, JMeter's affordability and accessibility make it suitable for those without extensive performance testing experience."
"It is an open-source tool that is easy to use. It can be easily integrated with multiple tools, including Selenium."
"JMeter is a free tool with a large user population, which comes in handy because we have a vast knowledge base to tap into when needed. It's also easier to hire consultants who know JMeter."
"The solution offers a lot of plug-ins and a huge continuously developing community that is regularly offering new features and plug-ins."
"The performance of the solution is excellent."
"JMeter's most valuable feature is the RegEx Extractor."
"We find the solution stable and scalable."
"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."
"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."
"Apache JMeter could be a more user-friendly product from the end user's perspective."
"Considering the kinds of tests we are performing here, where we launch several tests at the same time as a batch request, JMeter is not the best tool for the job. Those kinds of things could be done easily with other tools, like T6."
"It will be much easier, and beneficial for the individual to run it on their own machines rather than having a high-end infrastructure, more CPUs, or more memory that has been consumed by Apache JMeter."
"I need to consider it further because as features increase, it might become more complicated, and my goal has always been simplicity. Currently, I have to focus on other tasks, and I'm handling multiple responsibilities, so I can't juggle everything at once. However, if you ask me, I believe EJB covers most functionalities that are crucial. One improvement I'd suggest is adding a graphical aspect to the Gateway, making it a bit more colorful. Unlike JMeter, which lacks color, having a bit of color in the graphical aspects would be beneficial. Overall, for the essential features, EJB should work fine."
"The UI could be better."
"Apache JMeter's UI can be made more colorful."
"The UI of the solution needs to be better. The UI takes up a lot of our bandwidth."
"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.