-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
backport of #14058: speed up avoiding eta phi computations, and #14151: Slim down PFRecHit #15294
backport of #14058: speed up avoiding eta phi computations, and #14151: Slim down PFRecHit #15294
Conversation
tracked at #15151 |
please test |
The tests are being triggered in jenkins. |
A new Pull Request was created by @fwyzard (Andrea Bocci) for CMSSW_8_0_X. It involves the following packages: CondTools/Geometry @civanch, @Dr15Jones, @cvuosalo, @ianna, @mdhildreth, @cmsbuild, @alja, @slava77, @ggovi, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are list here #13028 |
-1 Tested at: 299d487 You can see the results of the tests here: I found follow errors while testing this PR Failed tests: UnitTests
I found errors in the following unit tests: ---> test runtestRecoEgammaElectronIdentification had ERRORS |
please test |
The tests are being triggered in jenkins. |
-1 Tested at: 299d487 You can see the results of the tests here: I found follow errors while testing this PR Failed tests: UnitTests
I found errors in the following unit tests: ---> test runtestRecoEgammaElectronIdentification had ERRORS |
@smuzaffar |
Looking at timing, apparently the effect is only about 3%, not as large as the 7% presented in the RECO meeting (change estimated before #15240 was merged).
Total per-job time changes from 0.379 s/ev to 0.371 s/ev, consistent with the total from the most relevant modules listed above. |
+1
@fwyzard it would be nice if you could check for the record the effect in your HLT setup using 8_0_16. I'm signing already, since even the 3% are worth it. The changes include backward-compatible data format changes and will need to be followed with dataset processing version change. |
Hi Slava,
yes, I plan to redo the tests with redirect to 8.0.16.
Ciao,
.Andrea
|
Neighbours buildNeighbours(unsigned int n) const { return Neighbours(&neighbours_.front(),n);} | ||
|
||
/// cell geometry | ||
CaloCellGeometry const * caloCell_=nullptr; |
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.
Since PFRecHit are storable, how can this work? ROOT will attempt to write out the CaloCellGeometry object since it was not marked as transient!
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.
Objection withdrawn. I didn't look far enough into the pull request changes.
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.
it's a pointer. Why would root try to write the actual CaloCellGeometry object?
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.
Because that is what ROOT I/O does when it encounters a pointer, it tries to write the object pointed to out to the file.
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.
Interesting. I didn't know that.
(the caloCell_ is transient, so this discussion is mostly academic)
backport to 8.0.x: