Skip to content
Snippets Groups Projects

Use DataPool for TRT_LoLumRawDataContainerCnv

In a heapTrack run of 100 ttbar events

one can see

 5 MOST CALLS TO ALLOCATION FUNCTIONS                                              
     6 21494650 calls to allocation functions with 7.66M peak consumption from         
     7 TRT_LoLumRawDataContainerCnv_p3::persToTrans(InDetRawDataContainer_p3 const*, InDetRawDataContainer<>*, MsgStream&)
     8   at /build/atnight/localbuilds/nightlies/Athena/23.0/athena/InnerDetector/InDetEventCnv/InDetEventAthenaPool/src/TRT_LoLumRawDataContainerCnv_p3.cxx:208
     9   in /cvmfs/atlas-nightlies.cern.ch/repo/sw/23.0_Athena_x86_64-centos7-gcc11-opt/2023-03-31T2101/Athena/23.0.23/InstallArea/x86_64-centos7-gcc11-opt/lib/libInDetEventAthenaPool.so

The idea here is to use a DataPool to avoid doing order of 200k small allocation per event

ping @ssnyder and @jchapman

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Christos Anastopoulos resolved all threads

    resolved all threads

  • This merge request affects 2 packages:

    • InnerDetector/InDetEventCnv/InDetEventAthenaPool
    • InnerDetector/InDetRawEvent/InDetRawData

    Affected files list will not be printed in this case

    Adding @cgrefe ,@calfayan ,@gemmeren ,@sroe ,@goetz as watchers

  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Please register or sign in to reply
    Loading