Details
-
Improvement
-
Status: Accepted
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
Minor
Description
This is the parent activity for supporting arbitrary parallel activity execution.
The ultimate aim is to allow as many sinks, sources and other activities to be executed in parallel, and also allow chains of pass-through and grouped activities to be executed in parallel.
Other issues will be created for the different stages and milestones.
Attachments
Issue Links
- clones
-
-
- Resolved
-
1.
|
Code to increment active lost from roxie |
|
Resolved | Richard Chapman |
2.
|
Investigate speed difference for teststd with enabled and disabled |
|
Accepted | Gavin Halliday |
3.
|
Consider spilling streams - multiple parts per channel |
|
Accepted | Jake Smith |
4.
|
Combining junctions and splitters? |
|
Accepted | Available for anyone |
5.
|
Automate spotting graphs to execute as parallel strands |
|
Accepted | Gavin Halliday |
6.
|
Check preservation and processing of PARALLEL in the optimizers |
|
Accepted | Gavin Halliday |
7.
|
Think through stream read-ahead implications |
|
Accepted | Gavin Halliday |
8.
|
Document the parallel language changes |
|
Resolved | Jim DeFabia |
9.
|
Revisit implicit choosen added to counts |
|
Accepted | Gavin Halliday |
10.
|
Revisit allocators for parse (and other activities?) |
|
Accepted | Unassigned |
11.
|
Implement parallel chains of grouped operations. |
|
Unresourced | Unassigned |
12.
|
Consider migrating strands to other slaves |
|
Accepted | Unassigned |
13.
|
Investigate using new strand helpers for parallel join |
|
Accepted | Jake Smith |
