[
https://issues.apache.org/jira/browse/FLINK-18695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17180388#comment-17180388
]
Yun Gao commented on FLINK-18695:
---------------------------------
Hi, I have finished the tests with the current master branch, and the detail is
in [this
doc|https://docs.google.com/document/d/1DiUjs_ft9qMSElhdDMkJlj_cIltYeghg4JKqnk3weCA/edit?usp=sharing].
Roughly, SSL would cause more memory consumption with both JDK and OPENSSL
provider, and the JDK provide seems to may cause memory consumption that cannot
be ignored.
In the next, I would also test the situation if JDK provider is changed to heap
buffer. I would finish the tests as soon as possible in the next several days.
> Allow NettyBufferPool to allocate heap buffers
> ----------------------------------------------
>
> Key: FLINK-18695
> URL: https://issues.apache.org/jira/browse/FLINK-18695
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Network
> Reporter: Chesnay Schepler
> Assignee: Yun Gao
> Priority: Major
> Fix For: 1.12.0
>
>
> in 4.1.43 netty made a change to their SslHandler to always use heap buffers
> for JDK SSLEngine implementations, to avoid an additional memory copy.
> However, our {{NettyBufferPool}} forbids heap buffer allocations.
> We will either have to allow heap buffer allocations, or create a custom
> SslHandler implementation that does not use heap buffers (although this seems
> ill-adviced?).
> /cc [~sewen] [~uce] [~NicoK] [~zjwang] [~pnowojski]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
