[
https://issues.apache.org/jira/browse/FLINK-36510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17911432#comment-17911432
]
He Pin commented on FLINK-36510:
--------------------------------
1. Another way to try is to limit the Netty's pageSize, eg :
`-Dio.netty.allocator.pageSize=1024` the default one is `8192`, and `-D
io.netty.allocator.numDirectArenas=1` because now there will be more Thread
Local cached arenas because Pekko is using the PooledByteBufAllocator too, this
is for performance .
Who will use a 7MB in production？
So If you think this is a problem, I think we can add a patch to pekko , which
let you configure how the pekko-remoting using ByteBufAllocator, a pooled one
or unpooled one, but the PooledByteBufAllocator will always have better
performance.
Another change in the current pekko release is the `FlushConsolidationHandler`
is added by default, I added that for performance, if you think that's bad, can
send a PR to make that optional too.
> Upgrade Pekko from 1.0.1 to 1.1.2
> ---------------------------------
>
> Key: FLINK-36510
> URL: https://issues.apache.org/jira/browse/FLINK-36510
> Project: Flink
> Issue Type: Technical Debt
> Components: Runtime / Coordination
> Affects Versions: 1.20.0, 1.19.1, 2.0-preview
> Reporter: Grace Grimwood
> Assignee: Grace Grimwood
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.0.0, 1.19.2, 1.20.1
>
>
> Updates Pekko dependency to 1.1.2 which in turn upgrades Netty 3 to 4
> (addressing FLINK-29065 and removing several CVEs from Flink). Pekko 1.1 also
> upgrades other dependencies such as slf4j and Jackson. For more details see
> the [Pekko 1.1 release
> notes|https://pekko.apache.org/docs/pekko/current/release-notes/releases-1.1.html].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
