[
https://issues.apache.org/jira/browse/FLINK-24553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Nowojski reopened FLINK-24553:
------------------------------------
> Change buffer debloating default configuration values
> -----------------------------------------------------
>
> Key: FLINK-24553
> URL: https://issues.apache.org/jira/browse/FLINK-24553
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Checkpointing
> Affects Versions: 1.14.0
> Reporter: Anton Kalashnikov
> Assignee: Anton Kalashnikov
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> After the investigation for buffer debloating effectiveness, there are some
> conclusion:
> * taskmanager.memory.min-segment-size can be decreased from 1024 to at least
> 256 because in some cases even 1024 is a too big value and at the same time
> the low min value is not a problem.
> * taskmanager.network.memory.buffer-debloat.samples can be decreased from 20
> to 10 or taskmanager.network.memory.buffer-debloat.period can be decreased
> from 500ms to 100ms or 200ms. According to the investigation, the current
> speed of reaction is too slow so it is better to increase it by changing one
> of these parameters.
> * taskmanager.network.memory.buffer-debloat.threshold-percentages can be
> decreased from 50 to 10 because there are no problems were found when the
> announcement of buffer size happened more frequently but it actually can
> positively influent the checkpoint time.
> it is better to change the default value for min-segment-size only after the
> task https://issues.apache.org/jira/browse/FLINK-24190 will be done.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
