[ntuple] Address some RNTupleProcessor performance bottlenecks#22593
Merged
enirolf merged 3 commits intoJun 16, 2026
Conversation
vepadulano
approved these changes
Jun 12, 2026
enirolf
force-pushed
the
ntuple-proc-chain-bottleneck
branch
from
be1986b to
0c7ea38
Compare
enirolf
force-pushed
the
ntuple-proc-chain-bottleneck
branch
from
724d342 to
d7d839b
Compare
Test Results 21 files 21 suites 3d 5h 44m 41s ⏱️ Results for commit d7d839b. ♻️ This comment has been updated with latest results. |
pcanal
reviewed
Jun 12, 2026
jblomer
approved these changes
Jun 15, 2026
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
4 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.
This change prevents the unnecessary re-connection of inner RNTuples in a chain upon calling
LoadEntry, by first checking whether the requested entry is before or after the currently loaded entry.In addition, some unnecessary calls to
InitializeandConnectinRNTupleSingleProcessor::GetNEntrieshave been factored out.