Skip to content

Conversation

@Tim-Brooks
Copy link
Contributor

The MockTcpTransport is not friendly in regards to memory usage. It must
allocate multiple byte arrays for every message. This commit uses reusable
big arrays for at least half of the allocated byte arrays.

The MockTcpTransport is not friendly in regards to memory usage. It must
allocate multiple byte arrays for every message. This improves the
memory situation by failing fast if the message is improperly formatted.
Additionally, it uses reusable big arrays for at least half of the
allocated byte arrays.
@Tim-Brooks Tim-Brooks added >test Issues or PRs that are addressing/adding tests :Distributed/Network Http and internode communication implementations v6.5.1 backport labels Nov 9, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

@Tim-Brooks Tim-Brooks merged commit 1919440 into elastic:6.5 Nov 10, 2018
Tim-Brooks added a commit to Tim-Brooks/elasticsearch that referenced this pull request Nov 10, 2018
…elastic#35425)

The MockTcpTransport is not friendly in regards to memory usage. It must
allocate multiple byte arrays for every message. This improves the
memory situation by failing fast if the message is improperly formatted.
Additionally, it uses reusable big arrays for at least half of the
allocated byte arrays.
@Tim-Brooks Tim-Brooks deleted the backport_tcp_mem_usage_to_65 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

backport :Distributed/Network Http and internode communication implementations >test Issues or PRs that are addressing/adding tests v6.5.1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants