BlazeMeter Initial Setup
I did most of the initial setup. We had to go through proxies and more when we connected to it. I currently use the Docker-based one because they support Docker and Kubernetes. At the moment, it's deployed in one or two locations, one is a sandbox for experimenting, and one in an actual development site, which is really good.
The initial deployment was very easy. It took a few hours. I forgot the proxy part, but once I did that, it was all good.
We can deploy a mock to build the application, and if we want to do it on-premises, as long as we have a Linux-based server, we can do it in 15 or 20 minutes. I was surprised because the moment it showed the hundreds of combinations for APIs that would happen, I was a bit shocked, but then I understood what it was doing.
I have a team of engineers who work on the solution and the different APIs that we need to support. I have two engineers who are really good with BlazeMeter. They were part of the virtualization team. There are a few engineers who started off with learning JMeter from YouTube and then did BlazeMeter University.
Most of the time, maintenance is done on the cloud. Because we are behind the proxy, we recently realized that when they did an upgrade, the upgrade failed and it took down the service. We provided that feedback, so the next time they do automated upgrades, we won't have any issues. Other than that, we haven't had any issues.
The SaaS account creation was very easy. Workspace creation was very easy. It's self-service, so those aspects were simple. Even the on-premises deployment is all Docker based. It's pretty advanced. They are clustering based, so having a cluster makes it easier. We didn't have an on-premises clustering solution like Kubernetes, so we had to go with the bare-bones Docker image implementation. We didn't have to do a lot of engineering because it's all self-service.
It took one year for our internal design to be done, approved, and implemented. The design involved allowing all of the connections from BlazeMeter as a load engine sitting on non-production infrastructure and applications. The network connectivity was done in one year. It was a massive implementation. We have 16 platforms, which can be considered mini-business units. We have our securities, treasury, retail banking, and internal corporate services.
The SaaS deployment took one day. They created the account and gave us access. My team was able to create workspaces. The on-premises deployment took a few hours. We went through all the connectivity and design. To complete the on-premises setup, we had to run a bunch of commands. Running the commands was easy and quick, but downloading hundreds of GBs of images took hours.
Two engineers were involved in the deployment. For the on-premises deployment, their role was to follow the instructions to complete the setup. After that, they had to verify if the setup was correct and then do end-to-end verification. A test was created in the SaaS portal, and we could choose the on-premises location and execute it to get results in the test portal.
Maintenance involves remediating vulnerabilities. BlazeMeter itself was not vulnerable. A Log4j vulnerability came out in December last year. BlazeMeter was pretty quick to respond. We quickly worked with our cyber team and service management teams. We were happy that it wasn't vulnerable because JMeter is used in BlazeMeter. JMeter uses Java, and the older version of JMeter has Log4j binaries. We weren't using those versions.
Our cyber team's direction was to get rid of those binaries if we weren't using them. The BlazeMeter team didn't have that policy, but they understood our stance. To address the risk, they upgraded and removed all of the old versions of JMeter from the platform.
We have auto updates enabled in our system for SaaS and on-premises. Maintenance is very light for us because of the auto-update feature. We have a small team for maintenance, but we're focusing more on addressing the customer knowledge gap because new teams and people are using BlazeMeter within our bank now.
View full review »From my company's side, I'm the "owner" of BlazeMeter. I worked with a support team to set up the on-premises infrastructure. I still work with them.
Deployment was straightforward and simple. We pulled some Docker images and deployed them. The whole on-premise deployment methodology is containerized, whether it's standalone unit servers running Docker or a Kubernetes deployment, which allows you to deploy on-premise BlazeMeter agents through a Kubernetes cluster and your own GCP environment or on-premises Kubernetes environment.
Buyer's Guide
BlazeMeter
March 2024
Learn what your peers think about BlazeMeter. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,234 professionals have used our research since 2012.
SG
Shivakumar_Gutte
Senior Manager at 360logica Software Testing Services
The setup process for BlazeMeter is simple.
View full review »SY
Steve Ybarra
QA Automation Engineer with 201-500 employees
Our DevOps team did all the setup, so I wasn't involved. We have faced challenges getting our functional test teams to engage with BlazeMeter. They don't have automation experience, so they're hesitant to pick it up and start using it. We've made a couple of attempts to show them how to get started with scriptless, but the incentive has not been good enough. Generally, it's still the regression team that handles the automation with Blazemeter, as well as whatever else we're using.
After deployment, we don't need to do much maintenance. Sometimes, we have to update test cases because they break, but BlazeMeter itself is low-maintenance.
YB
Yashb Bhatt
Vice President at Tenax Invest
I rate the setup phase of BlazeMeter a seven and a half on a scale of one to ten, where one is a difficult setup process and ten is an easy setup phase.
BlazeMeter can be deployed in three to four minutes, especially if the scripts and artifacts are ready, as users may only need to push the ready artifacts into their environments to trigger the deployment process.
The solution is deployed on the cloud.
MR
reviewer1511478
QA Automation & Perform Lead (C) at Canadian Tire
The deployment is very straightforward. That was one of our criteria, as we didn't want a complex new enterprise solution rollout. There were a few bumps during deployment, but most of that was on our side. BlazeMeter is relatively simple compared to other enterprise solutions we implemented.
Less than ten staff were involved in the deployment. We used Linux Enterprise to house the six on-premise load generators, and there were a couple of employees responsible for Docker, our solutions architect, and myself as the admin.
View full review »MA
Maria Aguas
Test Lead at World Vision International
The initial setup is not too complex. It mainly involves configuring IP addresses and server communication, but it is a basic process similar to other tools.
View full review »The product's deployment phase is fine and is not difficult.
I can't comment on the time taken to install the solution since our organization uses a shared installation with our enterprise account. My team didn't need to actually install the product, so we just created our workspace, and that was it.
The tool's implementation is done since my company deals more in mobile apps than web apps.
VB
reviewer2122104
VP QA Performance Engineer at a financial services firm with 1,001-5,000 employees
The initial setup of BlazeMeter is straightforward.
View full review »RS
Rahul-Sinha
Test Engineer at Deloitte
The initial setup is straightforward.
View full review »The initial setup is fairly simple. Deploying BlazeMeter is a quick process and it takes just a couple of minutes. You need to have an account with them, upload your test scripts from your local machine, and then configure and initiate the test.
The product's initial setup phase was simple.
The solution can be deployed in less than five minutes.
MD
reviewer1934670
Technology services specialist at a financial services firm with 1,001-5,000 employees
I was not involved in its deployment. In terms of maintenance, the only maintenance is setting up new servers for use. This configuration is usually performed by us in the Performance team.
View full review »AN
Anupam Narayan
Performance Engineer Manager at a financial services firm with 1,001-5,000 employees
I rate the product's initial setup around seven on a scale of one to ten, where one is a difficult setup, and ten is an easy setup.
The time taken for the deployment of BlazeMeter varies since we have multiple types of applications in our company. If I have to deploy something on BlazeMeter, the time range for the deployment process can be somewhere between 30 to 120 minutes.
The solution is deployed on the cloud.
The difficulty level for the installation of BlazeMeter depends on how we want to implement it. It's easy to download and install, but some companies restrict the security side of it. The paid solutions are more secure compared to these open-source solutions.
View full review »SM
reviewer2253501
Performance Test Engineer at a computer software company with 501-1,000 employees
The product's initial setup phase was user-friendly.
The solution is deployed on the browser.
The solution can be deployed in two to three days.
The product's initial setup phase was straightforward.
The product's installation deployment phase
The solution can be deployed in thirty minutes.
VK
reviewer1640346
Technology Specialist at a financial services firm with 10,001+ employees
The solution is very straightforward to implement. It's not overly complex or difficult.
The deployment only takes one week or so.
View full review »Initial setup was easy.
View full review »SV
Suresh Vaddi
Senior Engineer at CIBER
The initial setup is relatively straightforward and user-friendly. We have less than 50 users, we don't do any load tests.
For this audience, if you know JMeter, everything is pretty straightforward. You just sign up and upload your test. As far as support goes, if you do run into stuff, they have a little button on the side that lets you chat with them.
View full review »It was very straightforward to upload the JMeter scripts and supporting files, and start running tests.
View full review »Creating the JMeter test case required some time on our part, partially due to JMeter not supporting JavaScript and the application we were testing requires JavaScript support. We were able to create a test to work around that limitation, but that's more due to BlazeMeter utilizing JMeter than it being a limitation of BlazeMeter as a platform.
View full review »I found the initial setup to be pretty simple. I'm using JMeter, so I had to do a bit of research myself on how to change some of the JMeter settings that their Chrome add-on does not allow you to modify.
View full review »The setup was straightforward. We had a very simple setup. We had a very simple testing scenario. After I watched the one-hour video, how the thing works, and then it showed up your URLs to test, I entered that, and there were two options we had to choose. Technically, it was very straightforward just for pure load testing.
View full review »JC
John Mark Castro
QA Engineer at SSCGI
The initial setup was straightforward. I deployed it myself. Because I'm new to BlazeMeter it took two days to deploy because I needed to study it first also.
I deployed and also maintain it myself.
View full review »It was extremely easy to get set up.
View full review »The setup was pretty straightforward.
View full review »Initial setup is very easy.
View full review »The setup was straightforward.
View full review »Setup was straightforward and simple.
View full review »Buyer's Guide
BlazeMeter
March 2024
Learn what your peers think about BlazeMeter. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,234 professionals have used our research since 2012.