-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Using ConditionalTask
s make the HLT jobs take minutes to start
#38725
Comments
A new Issue was created by @fwyzard Andrea Bocci. @Dr15Jones, @perrotta, @dpiparo, @rappoccio, @makortel, @smuzaffar, @qliphy can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
assign core |
New categories assigned: core @Dr15Jones,@smuzaffar,@makortel you have been requested to review this Pull request/Issue and eventually sign? Thanks |
@fwyzard could you dump your configuration somewhere accessible? That would help in profiling. |
@Dr15Jones sure, I've just updated the description of the issue with the links to the configuration and input files |
Profiling showed that the slowdown was caused by calling some semi-heavy functions repeatedly, and with the complexity of the HLT menu then blowed up. #38730 provides a fix that reduces the the startup time close close to the job that used Tasks instead of ConditionalTask. I'll make a backport to 12_4_X as well. |
I can confirm that after cherry-picking #38730, the HLT menu using the
|
Thanks @fwyzard for the addtional test! |
+1 |
This issue is fully signed and ready to be closed. |
While testing the latest HLT menu
/online/collisions/2022/2e34/v1.2/HLT/V5
withCMSSW_12_4_2
and the124X_dataRun3_HLT_v4
global tag, I noticed that it takes a few minutes longer than usual to start.Adding the
Tracer
service shows:Following a suggestion by @missirol , I replace all instances of
ConditionalTask
with aTask
.This seems to solve the long startup time:
The problem can be reproduced using the configuration files at
and the input file at
with
The text was updated successfully, but these errors were encountered: