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
Traj float #5431
Traj float #5431
Conversation
A new Pull Request was created by @VinInn (Vincenzo Innocente) for CMSSW_7_3_X. Traj float It involves the following packages: DataFormats/TrajectoryState @civanch, @nclopezo, @lveldere, @mdhildreth, @cmsbuild, @StoyanStoynev, @slava77 can you please review it and eventually sign? Thanks. |
Hi Vincenzo, Is this reduction of 100MB expected from the first principles, On 9/19/14, 4:14 AM, Vincenzo Innocente wrote:
Vyacheslav (Slava) Krutelyov |
Indeed, I hope we do not have 5M LocalTrajectoryParameters objects floating around (we can count them...) |
I counted them btw today with CMSSW_7_3_X_2014-09-18-0200 |
+1 |
testing |
// to be moved inside a par section | ||
vector<Trajectory> theTmpTrajectories; | ||
|
||
/* |
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.
better get rid of it now, unless the point is to keep this as a somewhat obvious thing that doesn't work for future generations.
+1 for #5431 35ef3af Overall, no significant adverse changes in physics outputs, as expected from using floats instead of doubles. More numerically complicated outputs are affected slightly more: general tracks are almost unchanged, gsf/conversions are affected more; and even a bit more variation in the b-tag variables for single-particle guns (most num unstable parts). Based on MemoryCheck report in ttbar with run-1 PU running only RAW2DIGI,L1Reco,RECO,EI steps for 200 events: there doesn't seem to be much change in the peak memory usage
There seem to be some reduction in CPU, but this may be from some DB latencies
The above (wall-clock times) are in agreement with perf decreases with igprof. |
This PR contains two components:
1)
change double to float in LocalTrajectoryParameters.
for TTBAR 40PU25ns I observe a reduction of ~100MB of RSS for a very-small regression and no changes in tracking performances
No clue why was not done before (most probably less relevant at low pileup)
the original idea was to be able to access the "pt" of a seed w/o converting to a TSOS
it turns out that sorting seed in pt does not improve anything.
I prefer to keep it around for a couple of pre-releases, eventually remove (and clean code) if not useful in any way