Avoid un-necessary byte copies when decoding a Vert.x Buffer to a protobuf object and perform more optimal allocation #136
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.
Motivation:
The current implementation of the bridge uses a plain
ByteArrayInputStream
and then let protobuf parse the message. It turns out there is aKnownLength
interface used by the parser to know the actual buffer size to be decoded and optimize the decoding process.In addition we can use Netty
ByteBufInputStream
to avoid usingByteArrayInputStream
and un-necessary copies.Changes:
Swap usage of
ByteArrayInputStream
with a class that extendsByteBufInputStream
and implement KnownLength.