Skip to content

Conversation

@Tim-Brooks
Copy link
Contributor

Creating CompositeBytesReference has more overhead than a single
ByteBufferReference. Many of our messages will be contained to a
single ByteBuffer. This commit avoids creating composite instances
when there is 0 or 1 underlying ByteBuffers.

Creating `CompositeBytesReference` has more overhead than a single
`ByteBufferReference`. Many of our messages will be contained to a
single `ByteBuffer`. This commit avoids creating composite instances
when there is 0 or 1  underlying `ByteBuffers`.
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

Copy link
Contributor

@original-brownbear original-brownbear left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Tim-Brooks
Copy link
Contributor Author

No need to backport this as nio is not on 6.x.

@Tim-Brooks Tim-Brooks deleted the maybe_not_composite branch December 18, 2019 14:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Distributed Coordination/Network Http and internode communication implementations >non-issue v7.0.0-beta1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants