Optimize Target
and FieldSet
operations (Cherry-pick of #18917)
#18949
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.
Recent profiles (from #18911, and reproduced locally) highlighted:
FieldSet.create
was repeatedly calling the unmemoized_get_field_set_fields
, which used the surprisingly expensivefrom typing import get_type_hints
.Target.has_fields
was doing an N^2 lookup of fields in a computed collection of registered fields.field_values
dict
to represent the set of present fields, and removed theplugin_fields
property (which is always incorporated into thefield_values
at construction time anyway).Performance for
./pants --no-pantsd dependencies ::
inpantsbuild/pants
improves by 9% (or 15%, if the time for rule graph solving is ignored).