Profiling muon reco t139

1
Profiling muon reco t139

• Paul Balm
• April 12, 2001

2
Outline

• Looked at
• segmentreco, Combinatorial alg
• muo_trackreco, Fit alg (max 6 iters)
• Measurement details
• t01.39.00-maxopt on d0mino
• head version of muo_hit
• single muons with 1.1 minbias (1000 evts)
• jobs run in batch

3
Combi seg alg

• CombinatorialSegmentBuildergetSegments(PDTHitCol
  lection, MDT..., MSC...) 15.4ms
• 13.1 ms - MuoSegmentAlgCombifindSegme
  nts(MuoHitCollection)
• 2.5 ms - conversion to
  MuoHitCollection
• MuoSegmentAlgCombifindSegments(MuoHitCollection)
  takes 13.1 ms and calls
• 12.6 - createSegments(LocalWireHit
  Vec)
• 0.2 - createLocalHits
• 0.2 - matchSegments
• MuoSegmentAlgCombicreateSegments(LocalWireHitVec
  ) takes 12.6 ms and calls
• 10.1 - createSegments4Planes
• 2.5 - cleanSegments
• MuoSegmentAlgCombicreateSegments4Planes takes
  10.1 ms and calls
• 6.0 - MuoLocalSegmentaddHit
• 1.7 - MuoLocalSegmentfit
• 0.6 - MuoLocalSegmentMuoLocal
  Segment
• 0.7 - MuoSegmentAlgCombicreate
  Roads

4
Combi seg alg (2)

• MuoLocalSegmentaddHit takes 6.0 ms and calls
• 2.3 - LocalPoint(MuoLocalSegment,
  LocalWireHit)
• 2.1 - new delete
• 0.4 - LocalPointonTrack
• MuoSegmentAlgCombicleanSegments takes 2.5 ms
  and calls
• 2.5 - LocalSegmentintersect(Loca
  lSegment)
• MuoLocalSegmentintersect takes 2.4 ms (it's not
  just called by cleanSegments) and calls
• 1.7 - MuoIndexoperator

5
RecommedationsCombinatorialSegBuilder

• Recommendations for CombinatorialSegmentBuilder
• the newdelete in MuoLocalSegmentaddHit look
  like they could be removed
• MuoLocalSegmentintersect does a lot of
  comparing MuoIndices. If thats really necessary,
  speed up the comparison?
• conversion SegmentCollection to MuoSegmentVector
  takes 2.5 ms

6
MuoTrackAlgFit

• MuoTrackAlgFitfindTracks(SegmentCollection)
  takes 132.9 ms and calls
• 0 ms/event - conversion to
  MuoSegmentVector
• 132.9 ms/event - findTracks(MuoSegmentVector
  )
• MuoTrackAlgFitfindTracks(MuoSegmentVector)
  takes 132.9 ms and calls
• 132.9 - MuoTrackAlgFitfindT
  racks( pairltMuoSegmentVector,
  MuoTrackVectorgt )
• 0 - groupSegments
• MuoTrackAlgFitfindTracks( pairltMuoSegmentVector,
  MuoTrackVectorgt ) takes 132.9 ms and calls
• 132.7 - SegmentFitfit(Estim
  ation, TrackParameters, vectorltdoublegt )
• 0.2 - computeEstimation
• SegmentFitfit(Estimation, TrackParameters,
  vectorltdoublegt ) takes 132.7 ms and calls
• 127.6 - NonLinearFitterdoFi
  t(Estimation, Matrix)
• 4.9 - BackTrackParPropa
  gate(TrackParameters, doubles)

7
MuoTrackAlgFit (2)

• NonLinearFitterdoFit(Estimation, Matrix) takes
  127.6 ms and calls
• 105.4 -
  NonLinearFitterDerivative(Matrix, Matrix)
• 21.1 -
  NonLinearFitterParPropagate(Matrix, double
  double double)
• NonLinearFitterDerivative(Matrix, Matrix) takes
  105.8 ms and calls
• 104.6 -
  NonLinearFitterParPropagate(Matrix, double
  double double)
• NonLinearFitterParPropagate(Matrix, doubles)
  takes 125.9 and calls
• 125.6 - BackTrackPropagate
  (TrackParameters, doubles...)
• BackTrackPropagate(TrackParameters, doubles...)
  takes 125.6 ms and calls
• 85.8 - MagFieldPropagatorm
  agFieldPropagator(TrackParameters, double)
• 24.4 - ToroidinToroidLoc
• 3.7 - CartesianPoint
  constructors
• M.F.Prop.magFieldPropagator(TrackParameters,
  double) takes 85.8ms and calls
• 22.1 - doStep(TrackParamet
  ers, SpaceVector)
• 17.1 - SwapXYZapply
  with SpacePoint 8.3, with SpaceVector 4.7
• 3.9 -
  MagFieldTrackfieldTrack

8
RecommendationsMuoTrackAlgFit

• 13 ms/event used by SwapXYZapply is spent in
  SpacePoint/Vector ctors/dtors - 10 ms/event in
  total
• caching the return values of unit() and mag() of
  SpacePoint (only if the methods are being called
  on the same SpacePoint more than once)
• Its all in the SpacePoints

9
Conclusions

• L3 unpacking 4 ms/event
• CombinatorialSegmentBuilder 15 ms/event
• LinkedListSegmentBuilder 32 ms/event
• MuoTrackAlgFit (max 6 iters) 133 ms/event
• (first estimate instantaneous)
• Overall Weve become pretty fast!