Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-10141

Reduce lock contention introduced with 1.5

    XMLWordPrintableJSON

Details

    Description

      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.

      Attachments

        Issue Links

          Activity

            People

              nkruber Nico Kruber
              nkruber Nico Kruber
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: