-
-
Notifications
You must be signed in to change notification settings - Fork 8.8k
Multi target memory reallocation optimization #11744
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
trivialfis
merged 8 commits into
dmlc:master
from
siqi-he:multi_target_memory_realloc_optimization
Oct 21, 2025
+108
−4
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
c519c05
update row partitioner for MultiTargetHistBuilder
siqi-he 812697a
add resize
siqi-he c353baa
lint
siqi-he 0930faa
Merge branch 'master' into multi_target_memory_realloc_optimization
hcho3 63ace8c
Merge branch 'master' into multi_target_memory_realloc_optimization
siqi-he 48f32e2
add TestPartitionerOverrun
siqi-he d852b14
update msg
siqi-he 80b1335
Merge branch 'master' into multi_target_memory_realloc_optimization
siqi-he File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do you need to resize this after the loop?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's meant to be a safeguard if page size decreases between different calls. if the number of pages has decreased,
LeafPartitionwhich iteratespartitioner_withfor (auto const &part : partitioner_)could touch on stale data. this wasn't a problem previously since we were clearingpartitioner_every time we callInitData.it does seem to me the scenario above is extremely rare, but since adding a resize in most situations won't do anything, i figured it is probably ok to include it. they will be redundant if the number of pages never decreases.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for sharing. In that case, would you like to help add a test?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done. i've added tests for both
HistUpdaterandMultiTargetHistBuilderthat stale partitioners would not write top_out_positionespecially when we perform an update using a data with large number of pages first then followed by an update using a data with smaller number of pages. let me know if there is any issue