[
https://issues.apache.org/jira/browse/BEAM-8212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16934636#comment-16934636
]
Maximilian Michels commented on BEAM-8212:
------------------------------------------
Interesting, I've not thought about the cost of adding timers for the global
window. It looks like we could skip them entirely. Perhaps this should be
handled for Flink only, instead of in the StatefulDoFnRunner.
Do you have any numbers on the potential slowdown?
> StatefulParDoFn creates GC timers for every record
> ---------------------------------------------------
>
> Key: BEAM-8212
> URL: https://issues.apache.org/jira/browse/BEAM-8212
> Project: Beam
> Issue Type: Bug
> Components: beam-community
> Reporter: Akshay Iyangar
> Assignee: Aizhamal Nurmamat kyzy
> Priority: Major
>
> Hi
> So currently the StatefulParDoFn create timers for all the records.
> [https://github.com/apache/beam/blob/master/runners/core-java/src/main/java/org/apache/beam/runners/core/StatefulDoFnRunner.java#L211]
> This becomes a problem if you are using GlobalWindows for streaming where
> these timers get created and never get closed since the window will never
> close.
> This is a problem especially if your memory bound in rocksDB where these
> timers take up potential space and sloe the pipelines considerably.
> Was wondering that if the pipeline runs in global windows we should avoid
> adding timers to it at all?
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
