Modified Timing service to be thread-safe #1245
Merged
Conversation
This file contains 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
The Timing service now records event information per stream and them does a reduction at end job. The service also uses a per thread stack to record module start times to properly handle unscheduled execution and task spawning cases where a module is called on the same thread as another running (but paused) module.
|
+1 |
|
This pull request is fully signed and it will be integrated in one of the next IBs unless changes or unless it breaks tests. @ktf can you please take care of it? |
ktf
added a commit
that referenced
this pull request
Oct 31, 2013
Multithreaded fixes -- Modified Timing service to be thread-safe
omiguelc
pushed a commit
to omiguelc/cmssw
that referenced
this pull request
Apr 10, 2024
bug fixes for tracktriplet
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The Timing service now records event information per stream and them does a reduction at end job. The service also uses a per thread stack to record module start times to properly handle unscheduled execution and task spawning cases where a module is called on the same thread as another running (but paused) module.