avoid re-evaluating to know if a package has changed #859
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.
Summary:
Context: Adding a random file to
fbcode/
does some recomputation in the graph that leads to 40s build time in the incremental case.When
fbcode/BUCK
is a dep, this is unavoidable since you need to traverse the entire graph to understand if you need to recompute anything. However, in the case of some targets like//aps_models/ads/gmp:launcher_with_publish
fbcode/BUCK
is not a dep, but since we check for nearby package files for the entire graph, we end up spending more time.#thanks jakobdegen for helping me figure out what causes additional 35s computation in dice when we add files to fbcode/
Reviewed By: JakobDegen
Differential Revision: D69714496