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

Posted to issues@beam.apache.org by "Sam Whittle (Jira)" <ji...@apache.org> on 2021/02/01 12:58:00 UTC

[jira] [Assigned] (BEAM-11727) Optimize ExecutionStateTracker

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

Sam Whittle reassigned BEAM-11727:
----------------------------------

    Assignee: Sam Whittle

> Optimize ExecutionStateTracker
> ------------------------------
>
>                 Key: BEAM-11727
>                 URL: https://issues.apache.org/jira/browse/BEAM-11727
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-dataflow
>            Reporter: Sam Whittle
>            Assignee: Sam Whittle
>            Priority: P2
>
> Showed up as 1.5% of CPU on Nexmark 11 streaming benchmark run.
> It appears to be using a ConcurrentSkipListSet and most of the cpu is relatedd to inserts/removes in that, involving the system hash of the entries as that is used for ordering.
> The consistent ordering is unnecessary. Additionally for other reasons, removal and iteration is already synchronized and so performance will likely be better just using a synchronized HashMap and synchronizing in the add case.



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