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

• Results are easy to read
• Tests can be run easily
• Tests can ben imported easily from jMeter

Incentivized

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

Incentivized

• BlazeMeter should not require the purchase of 2 dedicated IPs for each suite of performance tests.
• BlazeMeter should make custom packages cheaper than they are today when purchased for an enterprise and should include dedicated IPs in the package.
• BlazeMerer should have integration with Jenkins Pipeline 2.0.

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

Personally, I prefer using JMeter + Redline13, however we had some business folks that wanted to be able to run a few of their own tests. The non-technical individuals preferred to use Blazemeter because of its simple and intuitive UI.

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