... | ... | @@ -34,6 +34,11 @@ Consider following configuration as an example: |
|
|
![Simple configuration](http://teetime-framework.github.io/images/parallelism.png)
|
|
|
|
|
|
By default the first stage - stage A - is declared active.
|
|
|
Therefore it runs also all subsequent stages in its thread.
|
|
|
Suppose stage A and B are able to run parallel but stage C depends somehow on stage B.
|
|
|
In such case, it is useful to declare stage B active so it can run in its own thread. |
|
|
\ No newline at end of file |
|
|
Therefore it runs also all subsequent stages in its thread.
|
|
|
Now suppose stage A and B are able to run parallel but stage C depends somehow on stage B.
|
|
|
In such case, it is useful to declare stage B active so it can run in its own thread.
|
|
|
We call ```B.declareActive()```.
|
|
|
As a result, stage A and B run in separate threads.
|
|
|
Furthermore, as stage C remains passive, it runs in the same thread as stage B, as it is stage B's successor.
|
|
|
|
|
|
TeeTime will automatically choose the right pipes for you, so you do not need to think about the synchronization of the communication between the stages. |
|
|
\ No newline at end of file |