sPHENIX tracking discussion

["Osborn, Joe" <osbornjd AT ornl.gov>]

Hi Christof,

 

This basically tracks with everything else we’ve seen. After switching the seeding to vector containers, the modules that run over multiple containers (e.g. the tpc/silicon track matching) run way faster. Hugo saw substantial gains too when moving the cluster container to vectors. I think making these changes will prove substantial in the end once we add everything up.

 

---------------------------

 

Joe Osborn, Ph.D.

Associate Research Scientist

Oak Ridge National Laboratory

osbornjd AT ornl.gov

(859)-433-8738

 

 

From: sPHENIX-tracking-l <sphenix-tracking-l-bounces AT lists.bnl.gov> on behalf of Christof E Roland via sPHENIX-tracking-l <sphenix-tracking-l AT lists.bnl.gov>
Date: Monday, May 23, 2022 at 6:16 AM
To: Hugo Pereira Da Costa via sPHENIX-tracking-l <sphenix-tracking-l AT lists.bnl.gov>
Subject: [EXTERNAL] [Sphenix-tracking-l] TPC Clusterizer performance

Hi Everybody,

I ran a test of the tpcclusterizer performance using verctors to store the hit infformation instead of our
usual maps base hit storage containers. The performance change is rather dramatic.
The memory goes down from 4 to 2,4 GB/job and the execution time when processing the
tpc sectors in sequence (i.e. turning the threading off) goes down from 1.6 sec to 0.27 sec.
See slide attached below.

Cheers

    Christof