Repository navigation
fix(cloning): reduce redundant query graph allocations - #339
Merged
Merged
Conversation
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.
Complex query graphs were repeatedly copied during refresh preparation, pagination counts, ordered UNION compilation, and derived-table attachment, creating substantial allocation pressure.
This change skips root filters and orders that the consuming operation discards, reuses privately owned count/aggregate snapshots, compiles SQL Server ordered UNION branches without cloning, and compiles eligible derived tables/joins directly while copying their bindings. CTE hoisting and explicit wrapping policies retain the existing clone path; retained mutable query inputs remain isolated.
Validation: