BlazeMeter vs Flood IO vs Loader.io

BlazeMeter
BlazeMeter

26
15
11
Flood IO
Flood IO

6
0
1
Loader.io
Loader.io

49
0
15
- No public GitHub repository available -
- No public GitHub repository available -
- No public GitHub repository available -

What is BlazeMeter?

Simulate any user scenario for webapps, websites, mobile apps or web services. 100% Apache JMeter compatible. Scalable from 1 to 1,000,000+ concurrent users.<br>

What is Flood IO?

Flood IO is a self-service load testing platform, designed to allow anyone to easily test the performance of their website from a few hundred users, right to up to 1 million or more.

What is Loader.io?

Loader.io is a free load testing service that allows you to stress test your web-apps/apis with thousands of concurrent connections.

Want advice about which of these to choose?Ask the StackShare community!

Why do developers choose BlazeMeter?
Why do developers choose Flood IO?
Why do developers choose Loader.io?
What are the cons of using BlazeMeter?
What are the cons of using Flood IO?
What are the cons of using Loader.io?
    Be the first to leave a con
      Be the first to leave a con
        Be the first to leave a con
        What companies use BlazeMeter?
        What companies use Flood IO?
        What companies use Loader.io?
        What are some alternatives to BlazeMeter, Flood IO, and Loader.io?
        Gatling
        Gatling is a highly capable load testing tool. It is designed for ease of use, maintainability and high performance. Out of the box, Gatling comes with excellent support of the HTTP protocol that makes it a tool of choice for load testing any HTTP server. As the core engine is actually protocol agnostic, it is perfectly possible to implement support for other protocols. For example, Gatling currently also ships JMS support.
        Runscope
        Keep tabs on all aspects of your API's performance with uptime monitoring, integration testing, logging and real-time monitoring.
        Apache JMeter
        It is open source software, a 100% pure Java application designed to load test functional behavior and measure performance. It was originally designed for testing Web Applications but has since expanded to other test functions.
        Locust
        Locust is an easy-to-use, distributed, user load testing tool. Intended for load testing web sites (or other systems) and figuring out how many concurrent users a system can handle.
        AWS Device Farm
        Run tests across a large selection of physical devices in parallel from various manufacturers with varying hardware, OS versions and form factors.
        See all alternatives
        What tools integrate with BlazeMeter?
        What tools integrate with Flood IO?
        What tools integrate with Loader.io?
        Decisions about BlazeMeter, Flood IO, and Loader.io
        No stack decisions found
        Interest over time
        Reviews of BlazeMeter, Flood IO, and Loader.io
        No reviews found
        How developers use BlazeMeter, Flood IO, and Loader.io
        Avatar of StackShare
        StackShare uses Loader.ioLoader.io

        I don’t remember exactly how I heard about Loader.io. I think I was adding load testing services to Leanstack. I saw it was a SendGrid Labs project, so there would be competent people behind it. And since they had a Heroku Add-On it was easy to get started. Loader.io is cool because it’s super simple to set up.

        We have about 30 tests set up for different pages: loader.io setup

        When executing tests, you can see error rate and average response times. But we also check the Heroku logs to see if they are real errors.

        My biggest complaint: figuring out what load to set for your tests is difficult. We don’t understand the language they use and no one we’ve spoken to that has used Loader.io understands it either. We’ve been testing at 250 clients (maintain client load) for all of our tests on 2 dynos. That means a constant load of 250 people using the site over a minute, or so I thought. The number of requests at the end of the test suggests it’s more like 250 additional clients hitting the site every second for a minute. But I guess accommodating a higher load is better anyways? 250 concurrent users seems to be our average HN traffic spike so that’s why we went with that load.

        Avatar of Volkan Özçelik
        Volkan Özçelik uses Loader.ioLoader.io

        I use loader.io for distributed load testing.

        That especially matters when you have a cross-region load-balancer and you want to make sure how your app behaves on a global scale.

        How much does BlazeMeter cost?
        How much does Flood IO cost?
        How much does Loader.io cost?
        Pricing unavailable
        News about Flood IO
        More news
        News about Loader.io
        More news