[
https://issues.apache.org/jira/browse/FLINK-23452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Nowojski closed FLINK-23452.
----------------------------------
Fix Version/s: 1.14.0
Resolution: Fixed
Merged to master as 3cbdd783e4e..230f659e790
> Measuring subtask throughput
> ----------------------------
>
> Key: FLINK-23452
> URL: https://issues.apache.org/jira/browse/FLINK-23452
> Project: Flink
> Issue Type: Sub-task
> Reporter: Anton Kalashnikov
> Assignee: Anton Kalashnikov
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> In the first implementation, throughput could be measured for the whole
> subtask. The throughput calculation should take into account the numbers of
> bytes that were handled, the backpressure time and ignore the idle time. The
> main idea is to keep the balance between idle and backpressure time, so if
> the backpressure time is high we should decrease the buffer size to provide
> the configured handling time and vice versa if the subtask is idle time that
> period should be ignored from calculating the throughput. Otherwise, in the
> case of network bottleneck, we might have ended up with a small buffer size
> that’s causing the bottleneck in the first place but we are not able to
> increase it due to idle time reducing throughput and lowering the buffer size.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
