spawn through local queue if possible #29
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.
In this PR, if
spawn
happens in tne working threads, tasks are pushed into the local queue for locality. It also removes the local wake mechanism of futures.Remote
is renamed toHandle
for its new meaning.Benchmark shows up to 100% improvement on chain_spawn.
But there is a regression on ping_pong when
ping_count
is large. This is because it is much more expensive to increase the capacity of crossbeamWorker
(allocating new buffer and copying all) thanInjector
(just adding a new block).