-
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
use ReadPrescalesFromFile=False
in the GenericTriggerEventFlag
of a bunch of DQM modules
#46530
use ReadPrescalesFromFile=False
in the GenericTriggerEventFlag
of a bunch of DQM modules
#46530
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-46530/42393 |
A new Pull Request was created by @mmusich for master. It involves the following packages:
@antoniovagnerini, @cmsbuild, @nothingface0, @rvenditti, @syuvivida, @tjavaid can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild, please test |
ReadPrescalesFromFile=False
in the GenericTriggerEventFlag
a bunch of DQM modulesReadPrescalesFromFile=False
in the GenericTriggerEventFlag
of a bunch of DQM modules
+1 Size: This PR adds an extra 12KB to repository Comparison SummarySummary:
|
ReadPrescalesFromFile=False
in the GenericTriggerEventFlag
of a bunch of DQM modulesReadPrescalesFromFile=False
in the GenericTriggerEventFlag
of a bunch of DQM modules
Removing RFC, as form the tests there seems to be no obvious downsides. |
+1
|
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @rappoccio, @antoniovilela, @mandrenguyen, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
Just to record, the MaxMemoryPreload shows about 13.7 MB reduction in step3 (reco+DQM) in some 2024 MC workflows such as
|
Thanks for the report. Out of curiosity, are you reading this off this table ? |
Yes. We are working towards getting such memory changes reported in the PR test summary message, but it will take some time (partly to build up experience on its behavior to minimize false positives). |
PR description:
Spinned off from #46448 (comment).
Reading L1T prescales from an 8 years old file looks wrong. Should help mitigating #46448.
PR validation:
None, other than compiling
If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:
Will be backported to active data-taking cycles if validates OK