Feature #15383
Milestone #15372: art multi-threading phase 1
Feature #15380: Introduction of multi-threaded running
Introduce StreamSchedule, etc.
Start date:
01/30/2017
Due date:
% Done:
100%
Estimated time:
(Total: 552.00 h)
Spent time:
224.00 h (Total: 586.00 h)
Scope:
Internal
Experiment:
-
SSI Package:
art
Description
This is in section 3, item 3, in the milestones document version 6.
Subtasks
Related issues
History
#1 Updated by Marc Paterno almost 4 years ago
- Blocked by Feature #15381: Migrate code from CMSSW FWCore/Concurrency added
#2 Updated by Marc Paterno almost 4 years ago
- Blocked by Feature #15382: Introduce thread-pause signaling for debugging added
#3 Updated by Marc Paterno almost 4 years ago
- Blocks Feature #15390: Introduce "one" modules added
#4 Updated by Kyle Knoepfel almost 4 years ago
- Status changed from New to Accepted
#5 Updated by Paul Russo about 3 years ago
- Status changed from Accepted to Work in progress
#6 Updated by Paul Russo about 3 years ago
- Status changed from Work in progress to Under Discussion
#7 Updated by Kyle Knoepfel over 2 years ago
- Blocked by deleted (Feature #15382: Introduce thread-pause signaling for debugging)
#8 Updated by Kyle Knoepfel over 2 years ago
- Category set to Event Loop
- Status changed from Under Discussion to Closed
- Target version set to 3.00.00
- SSI Package art added
For each concurrent event, the implementation uses one schedule, one trigger-results inserter, and one end-path executor. The implementation can be adjusted to encapsulate all three into a "schedule", thus providing a greater match between the user's mental model and the implementation. However, that has not been done for art 3.00.00.