BlazeMeter vs. Spirent TestCenter

It is well suited for applications that are mission-critical or applications that can receive high traffic/transactions at unscheduled time periods. Using the load testing feature of BlazeMeter, we can test and ascertain the capacity of the application without the drawbacks of the usual Apache JMeter load testing which depends heavily on the host system from where the load testing is performed.

Incentivized

Spirent solution is well suited to qualify a Lan infrastructure bandwidth capacity or a device itself capacity such as a router or a firewall for example. But this solution in our case is also well suited to test a complex and numbered mpls environment. I would not recommend it to a small business as the solution is very expensive: châssis and card cost are expensive and the solution requires to be an advanced user in system, not only on network devices

Incentivized

• BlazeMeter takes the .jmx script that teams had written for JMeter. The transition from JMeter to BlazeMeter was seamless.
• BlazeMeter offers its own cloud and hence we did not have to set it up on-premise.
• BlazeMeter hits our application from various geographic locations that simulates real life users.

Incentivized

• Bandwidth test
• QoS and traffic type generation
• Software platform availability
• Technical Support

Incentivized

• Blazemeter reporting is very basic and shallow. There is no way to drill down or correlate. I can get better reports by using JMeter for free.
• Blazemeter is very costly. Testing with volumes of more than 1K cu is expensive, and can be done for much cheaper if a company/team is willing to invest a bit of time to figure out how to use cloud instances and jmeter slaves, and to write a basic script to collect resulting xml output.

Incentivized

• QA
• Various bugs to fix on software installation
• Technical documentation
• No Spirent classes available
• Lack to fix major issues such as ntp for latency calculation

Incentivized

7 because they lack to improve some major bugs we have exchanged about with them

Incentivized

Easy to setup to do API Performance Testing. Dashboard to showcase results Capability to showcase runtime results

Incentivized

In comparison with Blazemeter the closes competitor is JMeter but it has disadvantages like it is not a tool that can be use as a collaborative tool and works locally in a computer, Blazemeter is in the web so different people can access and run tests or collaborate do add, edit or delete the existent scripts.

Incentivized

I wasn't able to specifically test other big products but I did use other free products in the past such as iperf, but free softwares don't allow the same level of support ans ease to use than Spirent

Incentivized

• It helped positively by helping to identify the maximum capacity needed for high traffic periods
• Saved revenue by eliminating unwanted duplication of systems

Incentivized

• Allows to qualify a link or a project to validate end of this one
• Allowed to detect various configuration issues that were fixed right after
• Allow to use virtual machines for easy remote deploykents
• Neharive: upgrade can depreciate products and newer products have sometimes better bandwidth capacity but less features

Incentivized