Project

General

Profile

Support #1277

MAUS Tracker Recon: Speed and Memory Usage

Added by Santos, Edward over 9 years ago. Updated about 8 years ago.

Status:
Open
Priority:
Normal
Category:
Tracker
Target version:
Start date:
20 May 2013
Due date:
% Done:

0%

Estimated time:
Workflow:
New Issue

Description

While setting up large data production, speed and memory usage became an issue to optimise. Here is the fractional time consumed by different parts of MAUS while running a simulation with 1 tracker only:

Time
Simulation (beam+G4): 31%
MCDigitization: 19%
Tracker Clustering: 30%
SpacePoint Recon: 9%
Pattern Recognition: 10%
Kalman Fit: 2%

This already included an optimisation in the MCDigitization which made it much faster. 2000 spills with 2 particle events each take about 35min to run on a i7 3.4GHz processor. The main point I have to make here is that looping over MiceModules is very time expensive but I don't see how to avoid it.

Memory consumption is abnormal. The 4000 particle events simulated consume about 5Gb of RAM while performing simulation and full tracker reconstruction. There seem to be memory leaks in the object processors. I'll attach the valgrind trace for a short 10 spill run.

Please leave your feedback/suggestions.


Files

valgrind_out.log (20.7 MB) valgrind_out.log Santos, Edward, 20 May 2013 15:55
datacard.py (3.33 KB) datacard.py Datacard file. Santos, Edward, 22 May 2013 11:59
HelicalTest_tracker0.dat (426 Bytes) HelicalTest_tracker0.dat To be saved in: /src/legacy/FILES/Models/Configurations Santos, Edward, 22 May 2013 11:59

Related issues

Related to MAUS - Bug #1278: Potential memory leak when running tracker reconstructionClosedSantos, Edward22 May 2013

Actions

Also available in: Atom PDF