Hacker News new | ask | show | jobs
by seekbeak 587 days 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?

2 comments

Yev here -> if you have a ticket number I'd love to know it b/c that's not accurate and I want to make sure support is trained properly. If you're using more than 10TB of storage you'll experience no change. We've updated our blog post w/ more explicit information (apologies for confusion on this one).
Sure thing: #1084672

The exact wording was: "If you are interested in increasing these limits, we do offer a higher threshold to customers who commit to a minimum of 20TB of our B2 Reserve Capacity-Based Storage service through one of our reseller partners."

Yev here - I confirmed that that's definitely a PATH towards not hitting those limits, but no reason to pay for 20TB if you're not using that much (especially if you're not using a reseller). I'm working with the team to change some of that messaging. The TL/DR is that most people will NOT see a change (we did a lot of analysis on the back end to see whether the throttling of <10TB customers would affect their behavior and most won't see a thing). This has been in production since Wednesday, so if you're not seeing any changes, your use-case is likely unaffected.
Cloudflare R2 seems designed for migrating off of someone else
Funny you mention that, I am creating a test bucket with R2 at this very moment.