Add lookup table to TaskExecutionHost to eliminate hot-path allocations #12774
+60
−9
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.
Fixes #11959 (assuming this is the issue number - please update)
Context
EnsureParameterInitializedconcatenates strings on every parameter initialization:This allocates on the hot path during task execution.
Changes Made
TaskFactoryWrapper.cs
DisableLogTaskParameterKeysandDisableLogTaskParameterItemMetadataKeysdictionaries toPropertyDataPopulatePropertyInfo()during task factory initializationGetDisableLogTaskParameterKey()andGetDisableLogTaskParameterItemMetadataKey()to retrieve precomputed stringsTaskExecutionHost.cs
Testing
Notes
Keys are computed once per task factory and reused across all parameter initializations, eliminating allocations from the hot path.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.