We performed a comparison between Apache JMeter and BlazeMeter based on our users’ reviews in five categories. After reading all of the collected data, you can find our conclusion below.
Comparison Results: Since JMeter has limited scalability, BlazeMeter is the clear winner in this comparison.
"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 offers a lot of plug-ins and a huge continuously developing community that is regularly offering new features and plug-ins."
"I like the fact that JMeter integrates well with other tools."
"The recording and playback functionality is helpful."
"The most valuable feature for us is the available information on the forums and to be able to discuss and get answers from the people that are involved in using this tool."
"The reports and analysis tools are very good. They are the solution's most valuable features."
"Apache JMeter is stable."
"The most valuable features are the integration with Jenkins and the reporting."
"The orchestration feature is the most valuable. It's like the tourist backend component of BlazeMeter. It allows me to essentially give BlazeMeter multiple JMeter scripts and a YAML file, and it will orchestrate and execute that load test and all those scripts as I define them."
"In our company, various teams use BlazeMeter, particularly appreciating its cloud license software, which supports up to 5,000 users. BlazeMeter's cloud capabilities allow us to load test or simulate traffic from any location worldwide, such as Europe, North America, South America, Australia, and even specific cities like Delhi. So, with one cloud license, we can simulate user load from various locations globally."
"One thing that we are doing a lot with the solution, and it's very good, is orchestrating a lot of JMeter agents. This feature has helped us a lot because we can reuse other vendors' performance scripts that they have used with JMeter before."
"The feature that stands out the most is their action groups. They act like functions or methods and code, allowing us to reuse portions of our tests. That also means we have a single point for maintenance when updates are required. Instead of updating a hundred different test cases, we update one action group, and the test cases using that action group will update."
"The stability is good."
"Using cloud-based load generators is highly valuable to us, as we can test from outside our network and increase load generation without having to upscale our hardware as much. The cloud load generator is there when we need it and is the feature we leverage the most."
"They have good support documentation and when we have contacted them, they helped to guide us."
"It's a great platform because it's a SaaS solution, but it also builds the on-premises hosting solutions, so we have implemented a hybrid approach. BlazeMeter sets us up for our traditional hosting platforms and application stack as well as the modern cloud-based or SaaS-based application technologies."
"JMeter's reporting is extremely rudimentary. The fundamental reporting mechanisms need to be drastically improved. It doesn't utilize an automatic session management mechanism or methods other tools use like parsing cookies and variables. Everything needs to be done manually. There's no automation."
"Both scalability and stability could be improved in Apache JMeter."
"Automation is difficult in JMeter."
"You really need a technical team in order to really utilize the product."
"Apache JMeter could use improvement in reporting. Currently, it isn't easy to generate reports in PDF format. While receiving reports in PDF format is possible, it requires a lot of customization. Additionally, when comparing the load test to others solutions it could improve."
"Self-healing and page rendering for the end-users are not available in Apache JMeter."
"The memory utilization in JMeter is very poor."
"Given that Apache JMeter is a free and open-source tool, documentation improvement may not be a major concern, as it is mostly contributed on a voluntary basis. The essential information is already available. However, in terms of the interface, there are occasional bugs, and the tool may not address them as quickly as some users would like. Fixing defects and bugs might take a considerable amount of time, with users sometimes having to wait for several months or even a year for the next release to address specific issues."
"BlazeMeter has room for improvement in terms of its integration with GitLab, particularly in the context of CI/CD processes. While it has multiple integrations available, the level of integration with GitLab may need further enhancements. It is known to work well with Git and Jenkins, although the extent of compatibility with GitLab is uncertain."
"I don't think I can generate a JMX file unless I run JMeter, which is one of my concerns when it comes to BlazeMeter."
"BlazeMeter needs more granular access control. Currently, BlazeMeter controls everything at a workspace level, so a user can view or modify anything inside that workspace depending on their role. It would be nice if there was a more granular control where you could say, "This person can only do A, B, and C," or, "This user only has access to functional testing. This user only has access to mock services." That feature set doesn't currently exist."
"The product currently doesn't allow users to run parallel thread groups, making it an area that should be considered for improvement."
"The should be some visibility into load testing. I'd like to capture items via snapshots."
"Lacks an option to include additional users during a test run."
"Scalability is an area of concern in BlazeMeter, where improvements are required."
"I believe that data management and test server virtualization are things that Perforce is working on, or should be working on."
Apache JMeter is ranked 1st in Performance Testing Tools with 82 reviews while BlazeMeter is ranked 4th in Performance Testing Tools with 41 reviews. Apache JMeter is rated 7.8, while BlazeMeter 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 BlazeMeter writes "Reduced our test operating costs, provides quick feedback, and helps us understand how to build better test cases". Apache JMeter is most compared with Postman, Tricentis NeoLoad, Katalon Studio, OpenText LoadRunner Professional and ReadyAPI, whereas BlazeMeter is most compared with Tricentis NeoLoad, OpenText LoadRunner Cloud, OpenText LoadRunner Professional, BrowserStack and Perfecto. See our Apache JMeter vs. BlazeMeter 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.