[ 
https://issues.apache.org/jira/browse/FLINK-8674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372847#comment-16372847
 ] 

ASF GitHub Bot commented on FLINK-8674:
---------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/flink/pull/5526


> Efficiently handle alwaysFlush case (0ms flushTimeout)
> ------------------------------------------------------
>
>                 Key: FLINK-8674
>                 URL: https://issues.apache.org/jira/browse/FLINK-8674
>             Project: Flink
>          Issue Type: Sub-task
>            Reporter: Piotr Nowojski
>            Assignee: Piotr Nowojski
>            Priority: Major
>
> Changes in data notifications introduced alongside BufferConsumer 
> significantly degraded performance of 0ms flushTimeout.
>  
> Previously flushing after writing only record, effectively triggered only one 
> data notification for the sub-partition/channel to which this record was 
> written. With low latency improvements, this changed and flush is now 
> triggering data notifications for all of the partitions. This can (and 
> should) be easily fixed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to