Reduce allocation counts in a couple of places #1571
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.
Messing around with heaptrack in #1563, I identified a couple of places with relatively high allocation counts when running
simpleclient
(modified to do several connections in a row).In CertificatePayloadTls13::convert, we were unnecessarily doing a clone. Fixed this by converting that function to take
self
, and the two callsites to userequire_handshake_msg_move!
instead ofrequire_handshake_msg!
.In
ChunkVecBuffer::consume
, when a chunk is partially consumed, we were calling Vec::split_off, which always "Returns a newly allocated vector." Instead, use Vec::drain, which reuses the current allocation.In local testing, the change to
ChunkVecBuffer::consume
appeared to reduce allocations by almost 10%. I'll be curious to see if the CI run shows actual runtime performance.