-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support compressed Bytestream transfers for remote execution #12670
Comments
Assigning to Philipp for triage and prioritization. |
@coeuvre Could you have a look and apply a P-label that you deem correct? :) Quick guidance:
|
Thanks. I am happy to implement this. |
any movement on this feature? |
@chancila Thanks for checking in! I actually just this week thought of it and have found a colleague who would like to implement it :) We'll follow up with details here soon. |
Closing since this is implemented by #14041. |
Description of the problem / feature request:
The RE API is close to finalizing support for API-level compression on Bytestream (bazelbuild/remote-apis#168). Using compression is optional, but Bazel should support it at some point.
Feature requests: what underlying problem are you trying to solve with this feature?
Remote builds can use significant bandwidth. Compression reduces the bandwidth used, which can also lead to significant performance improvements for bandwidth-constrained network connections.
What operating system are you running Bazel on?
This applies to all operating systems that Bazel supports.
The text was updated successfully, but these errors were encountered: