[
https://issues.apache.org/jira/browse/FLINK-25646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17856683#comment-17856683
]
Jufang He commented on FLINK-25646:
-----------------------------------
Hi [~pnowojski]
{quote}does it mean for buffer debloating enabled, you have increased floating
buffers from 8 to 2000?
{quote}
yes.
As your suggestion, I tested the higher debloating target (5s), and the
throughput of job only decreased by 5%.
However, it may be difficult to find the best target value for different jobs,
and it may require multiple tests and adjustments. I think we need to find out
the reason and optimize the buffer debloating mechanism to make it easier to
configure the buffer size.
> Document buffer debloating issues with high parallelism
> -------------------------------------------------------
>
> Key: FLINK-25646
> URL: https://issues.apache.org/jira/browse/FLINK-25646
> Project: Flink
> Issue Type: Improvement
> Components: Documentation, Runtime / Network
> Affects Versions: 1.14.0
> Reporter: Anton Kalashnikov
> Assignee: Anton Kalashnikov
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> According to last benchmarks, there are some problems with buffer debloat
> when job has high parallelism. The high parallelism means the different value
> from job to job but in general it is more than 200. So it makes sense to
> document that problem and propose the solution - increasing the number of
> buffers.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
