Repository navigation
Timesorter thread barrier - #1142
Merged
Merged
Conversation
dsarrut
force-pushed
the
timesorter-thread-barrier
branch
from
October 6, 2026 09:12
196b999 to
16de9b3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As discussed in #1090, this PR is a follow-up to PR 1090 to further reduce the memory consumption of actors that use a
GateTimeSorterin multi-threaded simulations (CoincidenceSorterActor,DeadTimeActor,PileupActor). The change makes sure that the divergence ofGlobalTimebetween threads is limited, which also limits the amount of memory required for buffering digis in the time sorter. This is done by forcing the "faster" threads to wait for the "slower" ones to catch up. This mechanism only kicks in once in a while so the impact on the simulation speed is limited.