perf: use fast uproot.num_entries
method instead of TTree.num_entries
#1197
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.
uproot.num_entries
is a fast path to get the number of events. It should always be faster thanTTree.num_entries
. This may become noticeable for preprocessing very large filesets.The nanoevents factory should use
uproot.num_entries
aswell (at some point), in this PR I just removed the overhead of calculating it twice.