perf: do not copy metadata for each data file in summary#2674
Merged
Fokko merged 1 commit intoapache:mainfrom Nov 2, 2025
Merged
perf: do not copy metadata for each data file in summary#2674Fokko merged 1 commit intoapache:mainfrom
Fokko merged 1 commit intoapache:mainfrom
Conversation
f Please enter the commit message for your changes. Lines starting
3 tasks
Fokko
approved these changes
Nov 2, 2025
Contributor
|
@Anton-Tarazi This makes a lot of sense to me, thanks for digging into this and providing the patch 🙌 |
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
2 participants
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.
Resolves #2673
Rationale for this change
_SnapshotProducer._summary()copies the metadata for every added / deleted DataFile. This is pretty expensive. Instead we just copy it once at the beginning of the function and use the same value each DataFile.On my data, which overwrites a few million rows at a time, I saw the time for
table.overwritego from ~20 seconds to ~6 seconds.Are these changes tested?
Yes, existing unit / integration tests
Are there any user-facing changes?
Just faster writes :)