-
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
[Run3 PromptReco] TMVA in BaseMVAValueMapProducer<pat::{Electron,Muon}>
uses 11 MB memory per stream
#46449
Comments
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 |
assign PhysicsTools/PatAlgos |
New categories assigned: reconstruction,xpog @ftorrresd,@hqucms,@jfernan2,@mandrenguyen you have been requested to review this Pull request/Issue and eventually sign? Thanks |
assign CommonTools/MVAUtils |
assign ml |
type performance-improvements |
I can check if we can convert these models without changes. |
The thread had a further comment https://root-forum.cern.ch/t/rdataframe-multithreading-loses-events/49338/11
Do you know if this was resolved? (we want to avoid locks) |
From #46040 (comment)
The function
reco::details::loadTMVAWeights()
uses 11 MB memory per stream (1 thread/stream profile vs 4 thread/stream profile), corresponding to 87 MB in 8-thread PromptReco job.The function is called by
BaseMVAValueMapProducer<pat::Electron>
andBaseMVAValueMapProducer<pat::Muon>
constructors.Avoiding the replication would reduce PromptReco memory by 76 MB. I don't know if TMVA is thread safe (i.e. if it could be easily moved to a
edm::GlobalCache
). If it is not, then probably some other inference engine should be considered.The text was updated successfully, but these errors were encountered: