BlazeMeter vs. VisualCron

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

VisualCron does accommodate continuous file processing. Like packing and unpacking compressed files, splitting or merging files, sending E-mail's and executing queries on databases. VisualCron in less suitable for performing very complex operations on files like, arithmetic with numbers, dates or amounts. Very complex job scripts become cluttered. Debugging Job scripts is not easy.

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

• VisualCron can pack and unpack files from many types of packing methods.
• Clear job scripts with complex constructions can be written in VisualCron
• VisualCron provides a clear graphical overview of the situation of all jobs.
• VisualCron clearly indicates when a job has run into an error.

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

• VisualCron should more specifically indicate the root cause of an error.
• If copying a file goes wrong, VisualCron reports 'can't copy file'. I expect 'no read permissions from original' or 'no write permissions from destination'.
• VisualCron offers no way to execute a Job script line by line
• In VisualCron, nested loops cannot be created.

Incentivized

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

Incentivized

Questions and problems can be addressed to VisualCron 's support department via E-mail. I usually get a good answer from them fairly quickly. There is also a VisualCron forum where you can ask questions that will be answered by other VisualCron users.

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

For simple processes, VisualCron is easier to use and maintain. For complicated processes, Quadient Inspire offers more options. The graphical representations of waiting, running or completed jobs is adequate for both products. The logging of job actions is better in Quadient Inpire as in VisualCron.

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

• With VisualCron, I need 3 times less time to get file processing right.
• If a VisualCron job goes wrong I need twice as much time to find the problem.
• Visualcron does not run on Linux but on Windows which can make an upgrade and reboot take up to 6 times as long.

Incentivized