-
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
[13_3_X] Removal of StringCutObjectSelector from Muon trigger DQM #42348
Conversation
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-42348/36370
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-42348/36372
|
A new Pull Request was created by @caruta for master. It involves the following packages:
@nothingface0, @emanueleusai, @cmsbuild, @pmandrik, @syuvivida, @tjavaid, @micsucmed, @rvenditti can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
Please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-fce6b2/33866/summary.html Comparison SummaryThere are some workflows for which there are errors in the baseline: Summary:
|
Please remove commented out code. |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-42348/36382
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
Thank you @caruta |
Hi @caruta AFAIK the module was using ~150MB of memory before the fix according to studies shown to us by PPD. So the reduction you are seeing are in the same ballpark. Even a bit larger, but I assume there's fluctuations depending on what exactly is run on what kind of events. From that I would conclude that we can be pretty confident that your changes fix the issue and this can be merged. Thanks! |
I do not see RSS values, only virtual memory size . AFAIK, virtual size is not limiting the job execution. |
I guess then we should just enable profiling for the PR tests? |
I'd leave it to @perrotta to decide; my past experience with the |
We are in the week-end, and we can afford spending 24h for these tests, if we want to check it. Let do so. |
enable profiling |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-fce6b2/33970/summary.html Comparison SummarySummary:
|
looking at igprofMEM_GC_step3 in 136.889 apparently the memory profiling does not work: |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-42348/36437
|
Pull request #42348 was updated. @nothingface0, @emanueleusai, @cmsbuild, @pmandrik, @syuvivida, @tjavaid, @micsucmed, @rvenditti can you please check and sign again. |
Sorry, my bad: trying to make the squash working I've messed up things... |
Perfect, thank you @caruta (and sorry for the extra work, but clean commits will definitely help future developers of the package). Please go ahead |
A new PR has been created: 42437. |
PR description:
This PR removes the "StringCutObjectSelector" from the Muon trigger DQM, with the aim of solving the memory issues faced during the 2022 rereco.
The cuts on the reco muons and trigger objects are now applied explicitly, since they are few and identical for all trigger paths.
This PR will be backported down to the 124X release (used for the 2022 rereco).
PR validation:
Tested running the DQM module on some of the latest RelVal, and checked the agreement of the distributions. Also ran
runTheMatrix.py -l limited -i all --ibeos
and no failures were seen.