Specialize BytesMut::extend<u8> when its Vec-backed#829
Open
AdamGS wants to merge 1 commit into
Open
Conversation
AdamGS
changed the title
BytesMut::extend<u8> when its Vec-backed
Signed-off-by: Adam Gutglick <adam@spiraldb.com>
AdamGS
force-pushed
the
adamg/specialize-extended-vec
branch
from
June 15, 2026 19:04
02decdb to
dc47673
Compare
Author
|
Messed up an unsafe block, now fixed |
This file contains hidden or 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
1 participant
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 PR adds a specialized code path to extending
BytesMutwhen its backed by aVec. There are no external changes, only a private function and type with some tests.When benchmarking on my laptop (M3 Max MacBook Pro), the change to
put_slice_vec_extendis from 400 MB/s to 9846MB/s. Happy to bench on some Intel hardware if the data is interesting.