Optimize block_on by caching Parker and Waker #149
Merged
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.
async-io
's implementation ofblock_on
currently creates a new parker and waker on every invocation. This PR caches the parker and waker in a thread-local to improve performance. Most of this code is copied fromfutures-lite
's implementation ofblock_on
, as that crate already does exactly this, and the performance difference between these twoblock_on
implementations is why I looked into optimizingasync-io
in the first place.futures-lite (Red) vs async-io without this PR (Yellow)
futures-lite (Red) vs async-io with this PR (Yellow)
(Also see bevyengine/bevy#9626 for more context)