3 ms·
S3-backed CH merge trees are notoriously expensive due to the high API call rates. We have a table doing over 11M APi calls per day. What are you seeing?
by dangoodmanUT 3y ago
S3-backed CH merge trees are notoriously expensive due to the high API call rates. We have a table doing over 11M APi calls per day. What are you seeing?
- parhamn 3y agoIs anyone doing these on cloudflare r2 where the cost is significantly lower?
- cldellow 3y agoR2 is significantly cheaper for egress, but not for API calls. It's still cheaper for API calls, but only by 10%: - 1M GETs $0.36 (R2) vs $0.40 (S3) - 1M PUTs $4.50 (R2) vs $5.00 (S3)
- mikeshi42 3y agoI'd love to be using Cloudflare as our cloud provider, but it didn't seem to make a lot of sense for our use case. We were concerned with some of the performance benchmarks we've seen with R2 in the past (though they've probably have improved), not to mention our compute options become a bit more limited to bandwidth alliance clouds otherwise we'll be eating network egress fees (which I do hate with a HUGE passion). Though I can imagine if you're comfortable with one of the bandwidth alliance clouds already and can take a bit of a perf hit for search, R2 and Backblaze both can provide some cost savings depending on your workload.
- mikeshi42 3y agoWe use a mix of SSDs and S3 for storage depending on the workload - as you're right, merging on S3 is awful and we try to avoid it!
- deleted 3y ago[deleted]