Merged
Conversation
34c9a5f to
4c06c4a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Use Cloudflare R2 object store to avoid egress charges from GCS.
Some more context: we had the distillation training data on GCS bucket (in
us-central1), it's about ~150GB of data (mostly the logits). We've used Colab, Lambda and Vast for GPU rental, in most cases we can't control whether the VM is in GCPus-central1region, which led to some unexpected egress charges. To avoid the GCS egress charges, we will use R2 object store, which has no egress charges 1.Footnotes
this doesn't mean that reading from R2 is free, reading operations are still tallied up as class B operations and charged after a free tier, doc. ↩