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
Memory efficient implementation of timing information for HGCDigitizer module for Premix Workflow. #30867
Memory efficient implementation of timing information for HGCDigitizer module for Premix Workflow. #30867
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-30867/17227
|
A new Pull Request was created by @adas1994 for master. It involves the following packages: SimCalorimetry/HGCalSimProducers @cmsbuild, @civanch, @kpedro88, @mdhildreth can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins.
|
-1 Tested at: d71814e CMSSW: CMSSW_11_2_X_2020-07-21-1100 I found follow errors while testing this PR Failed tests: ClangBuild
I found compilation warning while trying to compile with clang. Command used:
See details on the summary page. |
Comparison not run due to Build errors/Fireworks only changes/No short matrix requested (RelVals and Igprof tests were also skipped) |
I ran the workflow to make sure it would run successfully, but without adding it to the default PR tests, the baseline plots aren't stored, so the comparison plots can't be generated. |
Okay, so I am guessing that not much left here to do on my part in this PR. Btw, @kpedro88 I have a question not necessarily related to this PR. Is it mainstream that developers look for open issues in CMSSW github and pick up issues to work on by their own, or does one have to go through some-kind-of-approval-process to work on something? For example, if I want to work on Open Issue #30968 , do I need to talk to people or am I allowed to just get started ? |
Anyone is welcome to work on any open issue*. To avoid duplicating effort, if you are starting to work on a certain issue, you may want to add a comment to that effect (so others are aware). * of course, if the solution has some impact on physics performance, it may require validation and approval by the appropriate DPG or POG, as usual. |
The PR for that is #30988. It became a bit more involved than initially expected, but hopefully it can be merged soon. |
please test |
The tests are being triggered in jenkins.
|
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+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, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
<The HGCDigitizer module, in it's current form, store timing information of all the incoming hits from the minbias events in PreMixStage1 of the Premix Workflow. This PR aims to drop the timing information from redundant hits from the minbias events, once a HGCal cell reaches it's fire-off threshold of accumulated charge.
I found the PR to improve the performance of the code in terms of CPU performance, reduced memory and disk usage. The quantitative figures are mentioned below -
CPU Performance -
For BaseLine Igprof summary, I got the following
###############################################################################
And for the new Premix method, I got
Disk Usage -
PHGCSimAccumulator_simHGCalUnsuppressedDigis_EE_DIGI. 2.57756e+08 4.29255e+06
PHGCSimAccumulator_simHGCalUnsuppressedDigis_HEfront_DIGI. 3.5771e+07 621998
PHGCSimAccumulator_simHGCalUnsuppressedDigis_HEback_DIGI. 7.30215e+06 119472
For my new method, disk usage
PHGCSimAccumulator_simHGCalUnsuppressedDigis_EE_DIGI. 6.85587e+07 4.08996e+06
PHGCSimAccumulator_simHGCalUnsuppressedDigis_HEfront_DIGI. 6.34798e+06 333652
PHGCSimAccumulator_simHGCalUnsuppressedDigis_HEback_DIGI. 760055 51035.3
MemoryInfo-
FOr the addPileup method, the new proposed procedure uses almost an order of magnitude less memory(as shown in the attached screenshot; Black background screenshot- Baseline method, White background screenshot- My new method
)
PR validation:
<I ran a validation test by comparing results from WorkFlow # 20634.0(standard mix) and # 20634.99(premix) using custom validation package here - https://github.com/amartelli/HGCTimingAnalysis/tree/TimingAnalysis_11_1_X >