BlazeMeter Reviews

The ability to push large numbers of simulated users at our applications and having access to detailed reports: This helps us to have peace of mind that our apps can stand up to production-level loads and beyond.

We no longer have to guess whether deploying new code will affect performance or not. This ensures we are ready to meet customer demand, even at peak traffic times.

I would like to have better insights when tests fail to run properly or when the load engines occasionally break. There have been times when a test fails to start, sometimes due to a bug in my script and other times due to a problem on BlazeMeter’s side, that have required contacting support. It would be better if the interface proved enough feedback via logs, etc., for me to determine the cause and possibly fix it without needing to wait for BlazeMeter support.

I have used BlazeMeter for three years.

Occasionally, we have long wait times or trouble starting tests.

One load engine was not sufficient to run the JMeter scripts that I’ve written. Scaling up to seven load engines largely eliminated these issues.

Support is adequate. Getting initial responses for support issues can sometimes be slow.

It was very straightforward to upload the JMeter scripts and supporting files, and start running tests.

It is somewhat expensive, but the amount of testing and peace of mind it gives us is well worth the cost.

We considered creating our own internal JMeter farm, but in the end decided BlazeMeter would do a better job of end-to-end testing.

If you are looking to improve your website performance and ensure maximum uptime by load testing your system from end to end, then there is no better solution that I have found. It is extremely simple to setup.

The metrics are a great feature for analyzing each test. Being able to see the errors compiled, along with their responses, has been very useful. 

We also love having the ability to compare multiple test results in one screen. The multi-test feature is very useful as well. The ease for creating tests in BlazeMeter has been wonderful.

It has allowed us to run performance tests in order to help determine if we can scale well.

The ability to run node.js scripts needs to improve.

I have used this solution for around two months.

We have not encountered any particular stability issues.

We have not encountered any scalability issues.

We did not previously use a different solution.

The setup was pretty straightforward.

It would be nice to have more flexible pricing options.

Having a simple setup and being able to get the tests up and running right away, is the key for this solution.

Other than URL testing, there are no pieces of this software that are actually useful to us.

We were planning to load test this product for a significant release. It was somewhat helpful.

There are only certain features that actually work. Their URL testing and JMeter tests work only if testing URLs. If testing anything else, like WebDriver tests using JMeter and BlazeMeter, they do not work.

We have used it for close to two years but we are planning to NOT extend our licensing.

We had stability problems several times and we lost all our credits.

We did have scalability problems.

Technical support was OK for some situations.

We did not use a previous solution.

Setup was straightforward and simple.

I feel it’s overpriced unless they fix several things on their end.

We did evaluate other options, but we chose this one because setup was easy.

Look for your needs. This product is not a complete load-testing solution. It does offer certain types of load testing like URL testing but, other than that, we did not find them useful.

I really like the ability to spin up as many load generators as I need, and get statistics on response times and the load generators themselves. BlazeMeter support and flexibility is also hugely valuable.

To accurately test load on a webserver it takes traffic (load) from multiple “load generators”.
A load generator is a machine running load testing software (like Jmeter).
Clearly, one couldn’t accurately test 10 load balanced webservers with traffic from a standard desktop.
If one did and saw performance issues, the most likely source would be the desktop doing the testing, or the connection.
If no performance issues were seen it could be that the desktop was not able to emulate the specified load.

One blind spot of Jmeter is it does not tell the user how many threads their machine can handle. Users need to know how to monitor. Most users don’t, and set the threads higher than the machine can handle.
Blazemeter:

- Handles all that complication and makes using Jmeter simple

- Has expert staff that can point you in the right direction if your tests are not working

- Allows users to select how many load generators (machines running Jmeter) will be used during a given test.

o There are a few different contract options (1 server, 5 servers)

o Custom contracts for any number of servers you need. I really appreciate their flexibility on the contracts.

Building an in-house group of load generation JMeter servers to load test usually takes time and effort. BlazeMeter makes all that simple.

I have used JMeter for 4 years and BlazeMeter on and off for 2 to 3 years.

There were some minor issues with stability.

We did not encounter any issues here. Scalability is one of the wonderful parts of working with BlazeMeter.

Technical support has been great.

I’ve used JMeter from several load generator servers I set up to work together.

Initial setup was easy.

If you don’t see the option you need, just ask them. You’ll be able to get a custom contract. It is not free, but it is a fantastic deal compared to anything else out there.

Most recently I have been using a custom contract with Blazemeter rather than a standard month to month contract. That allows me to pay by test hours times servers used. So I can spin up as many load generators as I need. The statistics on response times and the load generators themselves are standard Blazemeter features available to anyone with a contract. BlazeMeter support has several times helped me figure out what was going on with my tests, that saved me a chunk of time. It's always nice to have some insight from a true Jmeter expert.

We considered setting up our own set of load generation JMeter servers. We also looked at HPE LoadRunner and SoapUI.

BlazeMeter is an easy way to get really accurate results from JMeters that you already have without having to build a set of networked JMeters (e.g., one with the UI running a bunch GUI-less slave machines).

Ability to generate heavy load (up to 5000 concurrent users)

Provide performance transactions summary & statistics

These features are valuable because, in my company, there is a requirement for the product to support up to 5000 concurrent users. As a performance engineer, it’s important to have a tool (like BlazeMeter) to generate heavy load and at the same time provide a report that shows how the system behaved under the load and provide performance statistics.

By using this tool, a performance engineer was able to identify performance bottlenecks, and after fixes was applied, overall product quality improved.

It would be very useful if there was a mechanism to schedule performance runs.

For example, a mechanism to automatically schedule performance tests execution, by using the calendar scheduler. This way, it would be possible to schedule multiple runs overnight, without the need to manually start each performance test.

I have used BlazeMeter with JMeter 3.0 and Java 1.8 for six months.

Stability was great; no issues.

Scalability was great; no issues.

I did not contact support.

We did not previously use a different solution.

I think prices are reasonable.

Before choosing this product, we did not evaluate other options.

It is an excellent and reliable tool. I liked it very much.

Load generation over cloud is the most valuable feature. This feature is most valuable for us because we use BlazeMeter for load testing. This helps us procure the required load generation infrastructure.

I have used BlazeMeter personally and my experience has been:

Whenever we want to provision more load generators (10 or more), it takes too long to initiate the test. Sometimes, the load generators have not even started and after waiting for 10 minutes or more, we get to know that we need to restart. This creates an awkward situation, when the client is also monitoring live execution and waiting for the test to start.

I have come across multiple instances, where the actual test was run for x hours but the server hours that were deducted from my account, were on the basis of x+1 hours. I have to keep monitoring the usage report frequently and request for credit back of all such server hours. Although, I get them back without any argument with the BlazeMeter team but still, it creates an overhead for me.

It needs to improve the server hour calculation and the provisioning of load generation machines.

I have used this solution for more than six months.

We had some stability issues; sometimes the load generators do not start at all.

We encountered some scalability issues. The start time for load test increases with the increase in number of users to be simulated.

I would give the technical support a 5/10.

The setup was straightforward.

The pricing could be more competitive.

We did not evaluate any other options.

The ability to scale JMeter tests easily. This isn't possible with traditional load testing approaches.

BlazeMeter allows us to easily run our existing load testing solutions at massive scale.

All of our consultants can use BlazeMeter. Traditionally our tests were run in JMeter and this was limited to technical users. BlazeMeter allows the use of the same tests but in a more user-friendly environment where all of our consultants can run the tests and access the results.

BlazeMeter is a cost effective way to scale our existing JMeter load tests.

Running of multi-tests could be improved to make it easier to create them. Apart from that nothing else springs to mind.

The application has been stable in most of our tests to date. We experience the odd bug, but BlazeMeter are quick to resolve any issues.

We have tested up to hundreds of thousands of concurrent users and the system performed well.

Easy to use and effective.

Initial setup is very easy.

When selecting a vendor, I look at ease of use, support, product maturity, and their partner model.

BlazeMeter is a great solution to run your existing tests. You will need detailed knowledge of JMeter to get the most out of your testing and BlazeMeter offer comprehensive training if you are new to this.

• Easy to make small changes to the test without reconfiguration, so we could step increases in load and find the limits without risk in breaking the test scripts. Consistent testing allows for confidence in the results and ease of use by the team.
• Integration with New Relic - provides insight as to why the test had the results and how we can improve them. New Relic was already in our tool belt, so it was nice to not need to change to an unfamiliar tool.
  

Provided an easy to use tool to measure the performance of our most critical business application, along with the expertise of BlazeMeter to properly generate the test case.

It has allowed us to test the impact of vendor updates to their software on the performance of the web component, which we are now doing as updates get released (6 month release cycle, so only one retest thus far).

System Administrators are performing the testing, as the software isn't ours and we don't presently develop our own software this was a new need and we don't have anything to compare to other than anecdotal evidence from users. We were able to compare results post-testing by comparing Google Analytics data and found that the improvements we put into place as result of the testing did have positive effect on both pageload and generation timings along with improving the overall conversion rate for the tool as well.

It's a rather expensive tool for running just a few tests — which is our primary use case, if there was a pricing structure that met our use case price wouldn’t be of concern. Worth noting is that we requested they donate our use of the tool — and they did donate the tool for our use — so it did not cost us anything (which we are very thankful for as a nonprofit).

We encountered no stability issues in using it.

We encountered no scalability issues, though we were testing at relatively low volumes.

Any questions we had were addressed promptly by knowledgeable individuals.

We wanted a solution that was easy to interpret and wouldn't require custom tooling beyond building the test. JMeter was the right tool for the job, and BlazeMeter's expertise and easy to use interface allowed us to readily view and compare results without needing to build a custom workflow.

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.

Cost is critical as a non-profit, and they donated our access as noted prior. Functionality is also critical — and they had the function we needed, were easy to configure, and integrated with New Relic which saved us a lot of time.

The alternative was to use Open Source tools to analyze the results, this solution was selected as we felt it would be faster and easier than rolling a custom solution which just wasn't warranted for how simple our situation is.

It's free and easy to sign up and try, so give it a whirl and see if it meets your requirements. We found it met ours and more, helping us gain confidence from our customers and solve a nagging problem in the performance of a third-party application.