Jobs

2

Votes

1

Hacker News, Reddit, Stack Overflow Stats

GitHub Stats

Description

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.

What is
Blitz?

Build bulletproof, scalable solutions with Blitz - a simple and fun service for load testing web apps and APIs in the cloud. Blitz offers powerful yet simple capabilities including continuous monitoring, performance testing and remediation. Blitz enables you to instantly burst up to 50,000 concurrent users against your app in seconds from multiple points of presence around the world.

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.

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

Reviews of Loader.io, Blitz, and Flood IO

How developers use Loader.io vs Blitz vs Flood 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:

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.