[Do not merge] Benchmark Tokio executor vs Rayon #31
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is an experimental PR to try using Tokio in place of Rayon. Tokio also uses a work-stealing thread pool for execution, but has better support for mutexes and locks (see rayon-rs/rayon#592).
It turns out that these better locks come with significantly higher overhead, and tree hashing runs 3-4x slower on Tokio than it does on Rayon: 140ms (tokio) vs 40ms (rayon).
This branch needs to be compiled with
tokio_unstableenabled: