[
https://issues.apache.org/jira/browse/FLINK-23974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17440291#comment-17440291
]
Anton Kalashnikov commented on FLINK-23974:
-------------------------------------------
Also, the strange behavior in the case of channel skew load was found that
described in more details in https://issues.apache.org/jira/browse/FLINK-24578.
Unfortunately, such behavior isn't reproduced every time so it is not obvious
what is the true reason for this. So further investigation is required in
separate ticket.
> Decreased throughput with enabled buffer debloat
> ------------------------------------------------
>
> Key: FLINK-23974
> URL: https://issues.apache.org/jira/browse/FLINK-23974
> Project: Flink
> Issue Type: Sub-task
> Affects Versions: 1.14.0
> Reporter: Anton Kalashnikov
> Assignee: Anton Kalashnikov
> Priority: Major
> Fix For: 1.15.0
>
>
> According to task https://issues.apache.org/jira/browse/FLINK-23456, we have
> some performance drop when the buffer debloat is enabled:
> * for static load with throttling in source - 1-3%
> * for sinus shape load with throttling in source - 2-3%
> * for erratic load with throttling in source - 5-6%
> It needs to investigate the reason for that and try to improve if it is
> possible.
> It makes sense to write the microbenchmarks for these scenarios to reproduce
> the problem locally.
> Problem assumption:
> Highly likely the problem is the speed of reaction on increasing load. During
> the investigation, it needs to pay attention to the calculation throughput
> for different load profiles. It is possible that when the load is low we are
> decreasing the buffer size to a small value(maybe minimum value) and when the
> load gets back to high we need several iterations of the throughput
> calculation to reach the appropriate buffer size.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)