-
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
remote/performance: add gzip compression to HTTP remote cache #4575
Comments
Let's also add |
I'd like to make little patches to implement this as it blocks me now. |
It seems like it is pretty easy :) |
@excitoon That might help for some cache backends, but for people on say, Google Cloud Storage as their cache backend, it does not do compressive transcoding (this would be very expensive with respect to CPU time). What Jakob and I were discussing offline was a scheme to store compressed blobs in GCS, and then detect and decompress them in the bazel client. |
Yep, I know about buchgr/bazel-remote#12 , this is just a client-side thing. Anyway, it is at least a progress on this task! |
…`Accept-Encoding: gzip` header. bazelbuild#4575
…`Accept-Encoding: gzip` header. bazelbuild#4575
…`Accept-Encoding: gzip` header. bazelbuild#4575
Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 2.5 years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team ( |
This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please reach out to the triage team ( |
The Apache client supported gzip, but the new Netty client doesn't.
cc: @jgavris
The text was updated successfully, but these errors were encountered: