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
Pr80x l1t memory fixes #16085
Pr80x l1t memory fixes #16085
Conversation
…r, (2) release memory from parser back to system at the end of 'read' methods.
… in L1TMuonBarrelParamsHelper.
A new Pull Request was created by @rekovic for CMSSW_8_0_X. It involves the following packages: L1Trigger/L1TMuonBarrel @cmsbuild, @rekovic, @mulhearn, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are list here #13028 |
please test |
The tests are being triggered in jenkins. |
Some info on the change of memory usage by OMTF XMLConfigReader:
Reduction in actual physical memory consumption (in RES) is about 500m. |
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_8_0_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @smuzaffar |
Pull request #16085 was updated. @cmsbuild, @rekovic, @mulhearn, @davidlange6 can you please check and sign again. |
@@ -35,8 +35,8 @@ void L1TMuonBarrelParamsHelper::configFromPy(std::map<std::string, int>& allInts | |||
|
|||
setAssLUTPath(AssLUTpath); | |||
///Read Pt assignment Luts | |||
std::vector<LUT> pta_lut(0); pta_lut.reserve(19); | |||
std::vector<int> pta_threshold(6); pta_threshold.reserve(10); | |||
std::vector<LUT> pta_lut(19); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rekovic - careful - I believe that pta_lut should be reserve not resize - see that there is a push_back (but only 1 push_back.. ) on line 379 (this code is extremely confusing)
please confirm...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@davidlange6 Yes, you are right. Pushing back on pta_lut vector will place beyond index 18,
which is not good. Changing back to reserve for pta_lut.
Pull request #16085 was updated. @cmsbuild, @rekovic, @mulhearn, @davidlange6 can you please check and sign again. |
please test |
+1 |
The tests are being triggered in jenkins. |
This pull request is fully signed and it will be integrated in one of the next CMSSW_8_0_X IBs after it passes the integration tests. This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @smuzaffar |
+1 |
This PR contains 3 types of fixes concerning memory management by L1Trigger:
(free allocated memory before every return). This is already provided in 81x Fix memory leak in L1Trigger/L1TMuonBarrel/src/L1MuBMEUX #16061 by @davidlange6