[ 
https://issues.apache.org/jira/browse/FLINK-10141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nico Kruber updated FLINK-10141:
--------------------------------
    Affects Version/s: 1.5.0
                       1.5.1
                       1.5.3

> Reduce lock contention introduced with 1.5
> ------------------------------------------
>
>                 Key: FLINK-10141
>                 URL: https://issues.apache.org/jira/browse/FLINK-10141
>             Project: Flink
>          Issue Type: Bug
>          Components: Network
>    Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.5.3, 1.6.0, 1.7.0
>            Reporter: Nico Kruber
>            Assignee: Nico Kruber
>            Priority: Major
>              Labels: pull-request-available
>
> With the changes around introducing credit-based flow control as well as the 
> low latency changes, unfortunately, we also introduced some lock contention 
> on {{RemoteInputChannel#bufferQueue}} and 
> {{RemoteInputChannel#receivedBuffers}} as well as asking for queue sizes when 
> the only thing we need is whether it is empty or not.
> This was observed as a high idle CPU load with no events in the stream but 
> only watermarks (every 500ms) and many slots on a single machine.



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

Reply via email to