Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
The gist of pipeline parallelization is that, should a task involve several steps which could have been in parallel but must be completed serially for each task, we want to break them down so that the parallelization takes place.
This PR challenges the status quo.
Implementation
Even if nothing is done, there is already speedup, because the template is broken into 2, and now we have 3 parts:
On top, this code is now possible:
Here, we have 5 chunks of 10000 elements, each generated 0.1 second apart.
Fast 4G
Before this PR: 2.38s
After this PR: 1.73s
Progress
stream=Trueor can we infer?await client.connected()then push content changes through the outbox?