You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2021/04/28 18:17:00 UTC

[jira] [Updated] (BEAM-12247) Reduce memory allocations in InMemoryTimerInternals

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

Kenneth Knowles updated BEAM-12247:
-----------------------------------
    Status: Open  (was: Triage Needed)

> Reduce memory allocations in InMemoryTimerInternals
> ---------------------------------------------------
>
>                 Key: BEAM-12247
>                 URL: https://issues.apache.org/jira/browse/BEAM-12247
>             Project: Beam
>          Issue Type: Task
>          Components: sdk-java-core
>            Reporter: Daniel Kulp
>            Assignee: Daniel Kulp
>            Priority: P2
>
> Doing some profiling, there are a lot of unnecessary allocations occurring in InmemoryTimerInternals:
> 1) Every WindowTracing.trace call calls getClass().getSimpleName() which searches the class name for a "." and then creates a substring which is then discarded if tracing is not on.  This can be cached easily.
> 2) In setTimer, the column key (timerData.getTimerId() + '+' + timerData.getTimerFamilyId()) is computed twice each time which involves string builders, appends, etc...   



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