You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Stephan Ewen (Jira)" <ji...@apache.org> on 2020/05/27 20:16:00 UTC

[jira] [Resolved] (FLINK-17906) Simple performance improvements in WatermarkOutputMultiplexer

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

Stephan Ewen resolved FLINK-17906.
----------------------------------
    Resolution: Fixed

Fixed in
1.11.0 via 
  - 5353c47b6627e067a5c18d81bc8ff389a7de18d8
1.12.0 (master) via
  - 204536b4727367ecc9702bdc11f2df60a21f60bc

> Simple performance improvements in WatermarkOutputMultiplexer
> -------------------------------------------------------------
>
>                 Key: FLINK-17906
>                 URL: https://issues.apache.org/jira/browse/FLINK-17906
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / Core
>            Reporter: Stephan Ewen
>            Assignee: Stephan Ewen
>            Priority: Major
>             Fix For: 1.11.0
>
>
> The WatermarkOutputMultiplexer has some potential for performance improvements:
>   - not using volatile variables (all accesses are anyways from the mailbox of under the legacy checkpoint lock)
>   - Using some boolean logic instead of branches



--
This message was sent by Atlassian Jira
(v8.3.4#803005)