4 ms·
See https://news.ycombinator.com/item?id=34639212 https://news.ycombinator.com/item?id=34639212. They got suspended for using workers behind the CDN. > I’m dis
by ddorian43 3y ago
See https://news.ycombinator.com/item?id=34639212 https://news.ycombinator.com/item?id=34639212. They got suspended for using workers behind the CDN.
> I’m distributing low bitrate audio, and small images, mostly
This means the cache-size would be much smaller though.
- gen220 3y agoRight, but they were serving content that wasn't from R2 as far as I understand from that thread. Not trying to say they that justifies their treatment, only that it doesn't apply to my use case. They were also seeing ~30TB of daily egress on a non-enterprise plan, which would absolutely never happen in my case – 1TB of daily egress would be a p99.9 event. Re cache-size, maybe I've misunderstood what you mean by cache size limiting, but yeah that's my point – I don't need a massive cache size for my application. My data doesn't lend itself much to large and distributed spikes. Egress is spiky, but centralized to a few files at a time. e.g. if there were to be a single day where 1TB were downloaded at once, 80% of it would be concentrated into ~20 400MB-sized files.
- ddorian43 3y agoHe was ok by the terms though. Workers had/have the same terms as R2 before R2 got the new terms. > They were also seeing ~30TB of daily egress on a non-enterprise plan, which would absolutely never happen in my case – 1TB of daily egress would be a p99.9 event. I don't understand what media company you'll be competing against if you'll use just 30TB/month of bandwidth.