[
https://issues.apache.org/jira/browse/FLINK-15963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhijiang updated FLINK-15963:
-----------------------------
Description:
On sender side while writing the BufferResponse message, it always allocates
the new direct ByteBuf from netty allocator to write header part for every
message.
Maybe we can make use of a fixed ByteBuf to write header part for all the
BufferResponse messages, then verify how it effects the performance/memory
overhead in e2e/benchmark.
was:
On sender side while writing the BufferResponse message, it always allocates
the new direct ByteBuf from netty allocator to write header part for every
message.
Considering only one message is written in one channel at the same time, then
we can make use of a fixed ByteBuf to write header part for all the
BufferResponse messages. We can verify how it effects the performance in
practice/benchmark.
> Reuse the same ByteBuf while writing the BufferResponse header
> --------------------------------------------------------------
>
> Key: FLINK-15963
> URL: https://issues.apache.org/jira/browse/FLINK-15963
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Network
> Reporter: zhijiang
> Priority: Major
>
> On sender side while writing the BufferResponse message, it always allocates
> the new direct ByteBuf from netty allocator to write header part for every
> message.
> Maybe we can make use of a fixed ByteBuf to write header part for all the
> BufferResponse messages, then verify how it effects the performance/memory
> overhead in e2e/benchmark.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
