-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
[Phase2 RelVal] O(10 million) memory allocations per event by Phase2TrackerMonitorDigi::analyze()
#46510
Comments
assign DQM/SiTrackerPhase2 |
type performance-improvements |
New categories assigned: dqm @antoniovagnerini,@nothingface0,@rvenditti,@syuvivida,@tjavaid you have been requested to review this Pull request/Issue and eventually sign? Thanks |
cms-bot internal usage |
A new Issue was created by @makortel. @Dr15Jones, @antoniovilela, @makortel, @mandrenguyen, @rappoccio, @sextonkennedy, @smuzaffar can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
assign upgrade |
New categories assigned: upgrade @Moanwar,@srimanob,@subirsarkar you have been requested to review this Pull request/Issue and eventually sign? Thanks |
I think there's no real reason to keep any of the |
The PR was merged, so I think we can close the issue |
From #45854 (comment)
In Phase2 RelVal Reco job the
Phase2TrackerMonitorDigi::analyze()
seems to make O(10 million) memory allocations per event. According to the IgProf profile nearly all of these come from MessageLogger.I see several
edm::LogInfo("Phase2TrackerMonitorDigi") << ...;
calls there. I guess what happens is that thePhase2TrackerMonitorDigi
formats the Info-level messages and injects them into the MessageLogger queue, and MessageLogger then discards the messages because the default logging level is above Info.I'd suggest to either change the most frequent to
LogDebug
, in which case the message formatting will be compiled away by default, or change the logging pattern toin which case the lambda passed to
log()
will be called only if the logging level is at least Info (i.e. with the default MessageLogger configuration the lambda will not be called).The text was updated successfully, but these errors were encountered: