Conversation
Avoid copying unrelated project items when the console logger reads configuration descriptions. Keep snapshot locking, metadata isolation, and unfiltered consumers unchanged. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 8013ed0f-9ede-4eb7-a35b-835c87d73e76
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Reading project configuration descriptions copies every project item before discarding unrelated items. Only matching descriptions now incur snapshot allocations; locking, ordering, metadata isolation, and other consumers remain unchanged.
In the focused x64 .NET Framework benchmark with 10,000 unrelated items, allocations fall from about 1,024 KiB to 5 KiB per project-start event. This is not an end-to-end build measurement.