Backblaze Rate Limiting Policy for Consistent Performance

15 pointsposted a day ago
by taubek

6 Comments

telgareith

a day ago

Suicide. 25MB/s download, and they're not even reasonably cheaper than the competition.

StillBored

a day ago

I agree, that is slower than the internet connection at my house, which could just host a few TB of spinning rust attached via USB faster.

Before I moved to backblaze I was half seriously lining up a few friends to share a similar setup that would self replicate between our houses and provide a simple restic interface.

Besides, they do charge for egress over a certain threshold so it seems they are also capping how much they can make from some customers. I get that there are probably a few problematic ones, but it seems that the business should be able to figure which ones are causing problems and solve it that way, rather than punishing the smaller customers using them as a storage depot. Customers whichh go years with a low level of upload+transactions under the theory that should the need arise the entire repo can be pulled back down at a few hundred MB/sec in a manner of hours.

EricE

a day ago

"and they're not even reasonably cheaper than the competition."

Such as?

seekbeak

a day ago

Just emailed support and they've said this is already implemented, and you can only increase your limits if you commit to 20TB of storage.

Our production web app can easily makes more than 20 requests for images per second on the initial page load for a single user. B2s new 20 requests per second cap means that it will just take one person viewing to cause anyone else also trying to view the app at that second to get an empty white screen. Cloudflare cache will only mitigate this so much.

Anyone got non Amazon suggestions to migrate to ASAP?

thejazzman

a day ago

Cloudflare R2 seems designed for migrating off of someone else

seekbeak

a day ago

Funny you mention that, I am creating a test bucket with R2 at this very moment.