GitHub user uce opened a pull request:
https://github.com/apache/incubator-flink/pull/38 [FLINK-971] Configure PooledByteBufAllocator in NettyConnectionManager
...instead of using the default allocator
Configuration:
- 0 heap arenas,
- n direct arenas (where n = num incoming + num outgoing network IO threads), and
- bufferSize << 1 bytes page size.
Additionally, `OutboundEnvelopeEncoder` directly implements `ChannelOutboundHandlerAdapter` instead of the
`MessageToByteEncoder<Envelope>` wrapper to have tighter control of memory allocations.
You can merge this pull request into a Git repository by running:
$ git pull
https://github.com/uce/incubator-flink FLINK-971
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-flink/pull/38.patchTo close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #38
----
commit 59e0ab867ecef5602cb8e05109a3ffd019f94536
Author: uce <
[hidden email]>
Date: 2014-06-17T14:18:02Z
[FLINK-971] Configure PooledByteBufAllocator in NettyConnectionManager instead of using the default allocator
Configuration:
- 0 heap arenas,
- n direct arenas (where n = num incoming + num outgoing network IO threads), and
- bufferSize << 1 bytes page size.
Additionally, OutboundEnvelopeEncoder directly implements ChannelOutboundHandlerAdapter instead of the
MessageToByteEncoder<Envelope> wrapper to have tighter control of memory allocations.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at
[hidden email] or file a JIRA ticket
with INFRA.
---
Locked
