How much traffic can Shields handle?

[seanlinsley]

These past couple days I've been opening pull requests on any repo I see that isn't using Sheilds' SVG badges.

Am I DDOSing Shields?

Are there any metrics available (like Gittip's librato dashboard) that would help illustrate how many queries Shields is getting? Have there been any benchmarks performed to determine how many requests can be handled?

Recently I've been seeing the Heroku application error page more often than I'd like. If there's anything I might be able to do to help, please let me know.

[espadrine]

Glad you asked! I am working on some analytics data provision: http://img.shields.io/$analytics/v1. I make no claim of accuracy for now, because it is quite recent and the data isn't persistent yet. I'll try to include more information as well, to know how well the system is behaving, and maybe a dashboard page.

[seanlinsley]

Hmm, it's the Travis badge in particular that's consistently failing. Perhaps we're hitting an API rate limit?

[espadrine]

That's odd. The logs do show these issues, about a quarter of the requests have a request timeout. It can be caused by a slowdown on Travis' side. Basically, we do a HEAD and we don't send data back until we receive the headers from Travis, but Heroku stops requests that take longer than 30s.

[seanlinsley]

If a request to a third-party API takes longer than (say) 10 seconds, we might want to serve the last known good image generated.

[espadrine]

That's a good idea.

[espadrine]

Duped bug: #191

[espadrine]

I believe this is fixed.