-
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
Reduce the ECAL and HCAL GPU memory usage [12.5.x] #39579
Reduce the ECAL and HCAL GPU memory usage [12.5.x] #39579
Conversation
Allocate memory buffers based on the actual number of events, instead of always allocating the maximum size.
A new Pull Request was created by @fwyzard (Andrea Bocci) for CMSSW_12_5_X. It involves the following packages:
@cmsbuild, @mandrenguyen, @clacaputo can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
Pull request #39579 was updated. @cmsbuild, @missirol, @mandrenguyen, @clacaputo, @Martin-Grunewald can you please check and sign again. |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-0d338d/27932/summary.html Comparison SummarySummary:
|
+hlt |
backport of #39577 |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_12_5_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_6_X is complete. This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Allocate memory buffers based on the actual number of events, instead of always allocating the maximum size.
Update the HLT menus to remove the obsolete parameters, if they are present.
Reduces the total GPU memory from running the HLT with 4 jobs with 32 threads and 32 streams by about 25%:
Thanks to @VinInn for finding the issue and for the changes.
PR validation:
The full HLT menu runs on GPU (with 12.4.9 plus #39580) without issues.
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:
Backport of #39577.