Task based stream begin transitions #17982
Conversation
Schedule each module into its own task when processing a stream begin Run or begin LuminosityBlock transition. All modules are allowed to run simultaneously without any inter-module dependencies.
Exactly where each piece of context for an exception message was being applied was dependent upon the type of transition which was running. Attempted to make this more uniform.
|
A new Pull Request was created by @Dr15Jones (Chris Jones) for master. It involves the following packages: FWCore/Framework @cmsbuild, @smuzaffar, @Dr15Jones, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here #13028 |
|
please test |
|
+1 |
cmsbuild
added
core-approved
fully-signed
and removed
core-pending
pending-signatures
labels
|
The tests are being triggered in jenkins. |
|
This pull request is fully signed and it will be integrated in one of the next master IBs after it passes the integration tests. This pull request requires discussion in the ORP meeting before it's merged. @Muzaffar, @davidlange6, @smuzaffar |
|
Comparison job queued. |
|
+1 |
Switched to using per module tasks for stream begin Run and begin LuminosityBlock. All tasks for a transition are scheduled simultaneously thereby allowing multiple modules to run. During these stream transitions, there should be no inter-module dependencies.