Consolidate Worker handling in UnscheduledCallProducer #12731
Conversation
As a first step to begin migrating to multiple threads per event we need to change how unscheduled is handled. Start by consolidating handling of unscheduled Workers into parts that change and parts that remain stable to avoid false sharing across cache lines.
|
A new Pull Request was created by @Dr15Jones (Chris Jones) for CMSSW_8_0_X. It involves the following packages: FWCore/Framework @cmsbuild, @smuzaffar, @Dr15Jones, @davidlange6 can you please review it and eventually sign? Thanks. Following commands in first line of a comment are recognized
|
|
please test |
|
+1 |
|
The tests are being triggered in jenkins. |
cmsbuild
added
core-approved
fully-signed
and removed
core-pending
pending-signatures
labels
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_8_0_X IBs after it passes the integration tests. This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @Degano, @smuzaffar |
…lProducer Consolidate Worker handling in UnscheduledCallProducer
As a first step to begin migrating to multiple threads per event we
need to change how unscheduled is handled. Start by consolidating
handling of unscheduled Workers into parts that change and parts that
remain stable to avoid false sharing across cache lines.