You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Acts-Athena track finding performance seems to be 5x slower than the legacy Athena implementation. I create this ticket do have a general overview where we can then branch out if specific action items.
There was no specific part of our CKF implementation that is responsible for the overall increased CPU time compared to legacy Athena but rather everything is slower.
If we require a refitting step after the CKF anyways - this depends on the physics performance we get after the CKF compared to something with a refitting stage - we could consider disabling/removing the calibration as a whole.
In the discussion it was said that we drop 90% of the tracks after the finding which might be too large to justify a full track fit before running a selection.
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.
Acts-Athena track finding performance seems to be 5x slower than the legacy Athena implementation. I create this ticket do have a general overview where we can then branch out if specific action items.
There was no specific part of our CKF implementation that is responsible for the overall increased CPU time compared to legacy Athena but rather everything is slower.
Action items:
The text was updated successfully, but these errors were encountered: