-
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
Slow processing of reconstruction configuration #20220
Comments
A new Issue was created by @Dr15Jones Chris Jones. @davidlange6, @Dr15Jones, @smuzaffar can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
assign reconstruction |
see also #18800 |
@Dr15Jones |
@slava77 I'm afraid I no longer remember. I originally figured it out by scanning the documentation. |
assign xpog |
New categories assigned: xpog @vlimant,@simonepigazzini you have been requested to review this Pull request/Issue and eventually sign? Thanks |
The cost of |
I am not surprised that this kind of configuration is extra slow ... and likely could be avoided |
Using python's cProfile package I determined that 44% of the time reading in a standard reconstruction configuration is spent in
miniAOD_customizeAllMC
. The time in that routine is dominated by the three (indirect) calls torunMetCorAndUncForMiniAODProduction
and that routine is dominated by the three calls toRunMETCorrectionsAndUncertainties.__call__
. The__call__
each make one call toRunMETCorrectionsAndUncertainties.toolCode
. From there, the timing gets distributed across multiple callsdigging deeper
several of the branches have time in
addToProcessAndTask
which givesThe next largest contribution (at 21% of the time) is loading
DQMOfflineMC_cff.py
which all comes fromDQMOffline_cff.py
. The time inDQMOffline_cff
is split fairly fine (note: entries with less than 0.1 cumtime have been removed)The time in
DQMOffline_Trigger_cff.py
is just split evenly in other module loadsThe text was updated successfully, but these errors were encountered: