-
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
Improve L1TMuonBarrelTrackProducer #46640
Conversation
- Hold member data directly not via pointers - Changed interface to reflect data is always available - Fixed const correctness issues - Removed unnecessary virtual interfaces
This required moving the header file to follow CMS coding rules.
Moved producer header info into source.
This routine was found to do an excessive number of allocations.
cms-bot internal usage |
@makortel FYI |
please test |
The reason the allocations dropped is the code now only calls |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-46640/42551 |
A new Pull Request was created by @Dr15Jones for master. It involves the following packages:
@aloeliger, @epalencia can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
type performance-improvements |
-1 Failed Tests: RelVals RelVals-INPUT AddOn RelVals
RelVals-INPUT
Expand to see more relval errors ...
AddOn Tests
|
I was able to reproduce the problem locally and then used ee26979 is the first bad commit
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-46640/42623 |
Pull request #46640 was updated. @aloeliger, @atpathak, @cmsbuild, @consuegs, @epalencia, @francescobrivio, @perrotta can you please check and sign again. |
I switched on Debug output from the module and saw that the |
please test |
+1 Size: This PR adds an extra 20KB to repository Comparison SummaryThere are some workflows for which there are errors in the baseline: Summary:
|
+1 |
+l1 |
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. @sextonkennedy, @rappoccio, @mandrenguyen, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
PR validation:
Ran step3 of workflow 12861.0 with improved ModuleAllocMonitor. Previously each event processed by the module needed 85k allocations. Now only the first event of each stream uses that much and all subsequent only use 19 allocations.
This should strictly be a technical change and should have no effect on the results.