-
-
Notifications
You must be signed in to change notification settings - Fork 661
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
GoStdLib is slow with remote caching / execution #2188
Comments
Regrettably it's a known issue that the The only thing that changed between those versions is the default Go version, so perhaps that simply invalidated the cache? Nothing about the implementation changed. |
Would pre-packaging the inputs for |
Just checked: 6148 files |
To avoid uploading/downloading this to/from the remote cache you can try: |
I tried using the I've also tried bazel: 3.7.0 |
@derekperkins I've also noticed that remote caching with rules_go in a containerized environment usually increases build times by x2 to x5. Even without caching of gostdlib. It seems remote caching is far from being production ready. |
What version of rules_go are you using?
Upgrading from 0.19.1 to 0.19.2+
What version of gazelle are you using?
0.18.1
What version of Bazel are you using?
0.28.1
Does this issue reproduce with the latest releases of all the above?
Yes
What operating system and processor architecture are you using?
Linux EC2 instance c5.large
Any other potentially useful information about your toolchain?
rules_docker 0.7.0
Remote caching to Google storage bucket turned on
What did you do?
Using go_image to build the following:
results in a build time approaching 20 minutes
[55 / 78] GoStdlib external/io_bazel_rules_go/linux_amd64_pure_stripped/stdlib%/pkg; 1166s remote-cache, linux-sandbox
but only when using rules_go to higher than 0.19.1. Using 0.19.1, stdlib takes only about 10s.
What changed between releases that could cause this?
The text was updated successfully, but these errors were encountered: