-
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
[Phase2 RelVal] O(100 MB) memory held per event from HGCalGeometry::getGeometry()
in PFRecHit
s
#46511
Comments
assign geometry, upgrade |
New categories assigned: geometry,upgrade @bsunanda,@civanch,@Dr15Jones,@kpedro88,@makortel,@mdhildreth,@Moanwar,@srimanob,@subirsarkar you have been requested to review this Pull request/Issue and eventually sign? Thanks |
cms-bot internal usage |
A new Issue was created by @makortel. @Dr15Jones, @antoniovilela, @makortel, @mandrenguyen, @rappoccio, @sextonkennedy, @smuzaffar can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
@cms-sw/hgcal-dpg-l2 |
Are the cmssw/Geometry/HGCalGeometry/src/HGCalGeometry.cc Lines 699 to 724 in f71ff4c
If this is the case, how much memory would be needed to store these all the time? Or is the rationale something different? |
HGCalGeometry::getGeometry()
HGCalGeometry::getGeometry()
in PFRecHit
s
Adding @cms-sw/reconstruction-l2 @cms-sw/pf-l2 because of the connection to |
type performance-improvements |
From #45854 (comment)
The container of
PFRecHit
produced byPFRecHitProducer::produce()
ends up holding O(100 MB) memory per event (I suppose the exact value depends on the event itself) allocated inHGCalGeometry::getGeometry()
as shown in IgProf profile.Given the related issue #46433, I think the rationale for creating these geometry elements on the fly should at least documented, if not re-evaluated.
The text was updated successfully, but these errors were encountered: