Multiple streams in cmsRun #685
Conversation
To support concurrent event processing, we need to isolate the event handling from the rest of the transition handling. This is the first step.
Since the state machine makes certain useful guarantees when doing an Event transition, I moved the contiguous event loop into the method called by the state machine when an event in encountered. This will later change to be where the different Stream tasks are launched.
Stream modules and modules which have Run, Lumi or Stream caches needs to know how many 'slots' to reserve. This gets the information down to where modules are constructed.
Percolated the PreallocationConfiguration into the module base classes and passed the number of streams to the appropriate virtual functions which are overwritten in the appropriate inheriting classes. The per Run and LuminosityBlock items are still just single items since having multiple such transitions is a later phase of the project.
If more than one stream is requested in the configuration, create them and then distribute the events using a round-robin algorithm.
…ltipleStreamsInEventProcessor Resolved minor overlapping change in EventProcessor.cc and SubProcess.cc. In both cases the resolution was to use the change already in this branch.
|
A new Pull Request was created by @Dr15Jones (Chris Jones) for CMSSW_7_0_X. Multiple streams in cmsRun It involves the following packages: FWCore/Utilities @civanch, @Dr15Jones, @mdhildred, @giamman, @ktf can you please review it and eventually sign? Thanks. |
|
+1 -This commit was merged with CMSSW_7_0_X at approximately 1700 on Sept 1 (CERN time). @nclopezo please run the standard suite of tests on this change |
|
@Dr15Jones I tested it last night. Jenkings log. All passed. |
|
+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. |
Config for LO NNPDF30 PDF needed for commit cms-sw#685
Provides full support for creating multiple streams in cmsRun.