-
Notifications
You must be signed in to change notification settings - Fork 278
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
Reduce disk space usage of the rules #2641
Comments
To start, do we need rules_apple/apple/internal/processor.bzl Lines 570 to 576 in c5a3307
|
I don't think we need it. |
This output, as the comment says, is intended for Tulsi which is now deprecated. As part of #2641 we are removing this output to save on disk space utilization.
This output, as the comment says, is intended for Tulsi which is now deprecated. As part of #2641 we are removing this output to save on disk space utilization.
Turns out the comment saying this was for Tulsi only is incorrect, its the archive used when not using tree artifact outputs. |
FWIW i think the unprocessed archive predates the quality tree artifact support in bazel in general. back in 2018 those just didn't work at all. so i imagine there is some way to eliminate it at this point. |
Yeah id love to make tree artifacts the default, theres this blocker right now: #2545 |
This is a general issue to describe the current disk space usage issues of some of the rules.
The current default is to not use the
use_tree_artifacts_output
flag, this mostly seems to be because of potentially now fixed issues in Bazel like: bazelbuild/bazel#16361. See also: #2545With the current default the disk space usage for a large-ish application target is >3x the size when compared to the tree artifact ouputs.
Without usage of the use_tree_artifacts_outputs flag (default):
With use_tree_artifacts_outputs flag:
For large projects this can add several hundreds of gigabytes to the output-base which means engineers need to frequently
bazel clean --expunge
to clear up disk space (or worse run into failed builds when they run out of disk space).This has also been a topic of concern for other users, see: #2638
The text was updated successfully, but these errors were encountered: