-
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
[HGCal] Shrinking Layer Clustering internal data structures #30753
[HGCal] Shrinking Layer Clustering internal data structures #30753
Conversation
The code-checks are being triggered in jenkins. |
@cmsbuild please test |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-30753/17072
|
The tests are being triggered in jenkins.
|
A new Pull Request was created by @felicepantaleo (Felice Pantaleo) for master. It involves the following packages: RecoLocalCalo/HGCalRecProducers @perrotta, @jpata, @cmsbuild, @kpedro88, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+upgrade |
The tests are being triggered in jenkins.
|
+1 |
Comparison job queued. |
running just the local HGCAL sequence in 8 threads I now get the peak RSS dropping from 9.0 GiB to 6.3 GiB. This is a really convincing improvement now. |
Comparison is ready Comparison Summary:
|
+1
|
+upgrade |
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. @silviodonato, @dpiparo (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
@tommasoboccali @fwyzard @srimanob do you want a backport of this PR to 11_1? |
@silviodonato there is already a backport in #30757 |
@silviodonato For additional PRs that affect RECO, we may review at the end for the minimal changes if benefit and see if we need limited validation for specific groups. |
PR description:
The memory footprint of the
HGCalLayerClusterProducer
grows with increasing number of events. This is solved byshrink_to_fit()
afterclear()
when resetting these data structures.