Speeding up histogram postprocessing in doHadd #284
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
1 participant
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.
Closing a rootfile with many histograms can take a long time; this can be sped up by using ROOT.gROOT.GetListOfFiles().Remove() (see https://root-forum.cern.ch/t/tfile-close-slow/24179)
This is already done within haddfast, but not when opening / closing the rootfile when doing histogram postprocessing
Since ROOT is not deleting the objects in memory when the file closes, they must be deleted manually instead
Tested and saw minor improvement in closing speed (30s to 6s) for a histogram file with 139k histograms; however analyses with more histograms could see larger improvement. If there are no such analyses, I will close this PR. :)