Open paulgessinger opened 2 years ago
This issue/PR has been automatically marked as stale because it has not had recent activity. The stale label will be removed if any interaction occurs.
This issue/PR has been automatically marked as stale because it has not had recent activity. The stale label will be removed if any interaction occurs.
The peak memory consumption of the track state EDM strongly increases when pileup and even complexity is increased. For ttbar events at $\mu=200$ from Pythia8, it can go up to a few gigabytes per event, which is suboptimal.
This issue tracks progress to improve and optimize the memory consumption.
Associated PRs:
1507
This helps centralize the
MultiTrajectory
usage: a single instance is used by the examples algorithms to accumulate tracks from all seeds1512
Switches from overallocating vectors and matrices for the measurements to using a jagged vector structure that looks like this:
1511
Implements statistics on the memory usage of
Acts::VectorMultiTrajectory
to give us an idea of what's going on.Status quo
The tooling from #1511 gives the following measurements from
MultiTrajectory
:ODD full chain example with Pythia8 ttbar @ mu200
ODD truth tracking with Pythia8 ttbar @ mu200
Other ideas