[
https://issues.apache.org/jira/browse/BEAM-11435?focusedWorklogId=522699&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-522699
]
ASF GitHub Bot logged work on BEAM-11435:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 10/Dec/20 12:55
Start Date: 10/Dec/20 12:55
Worklog Time Spent: 10m
Work Description: dmvk commented on pull request #13522:
URL: https://github.com/apache/beam/pull/13522#issuecomment-742503871
Run Java Flink PortableValidatesRunner Streaming
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 522699)
Time Spent: 0.5h (was: 20m)
> Reuse already set timers instead of recreating them in Flink Streaming Runner
> -----------------------------------------------------------------------------
>
> Key: BEAM-11435
> URL: https://issues.apache.org/jira/browse/BEAM-11435
> Project: Beam
> Issue Type: Bug
> Components: runner-flink
> Affects Versions: 2.23.0, 2.24.0, 2.25.0
> Reporter: David Morávek
> Assignee: David Morávek
> Priority: P1
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When we re-set a timer, new timer goes trough following life-cycle:
> 1) Find previously set timer with the same id
> 2) Cancel any previously set timer with the same id
> 3) Set a new timer
> We can skip 2) and 3), if the new timer is the same as previously set timer.
> There should be a great performance impact on GC timers, especially with
> RocksDB backend, where 2) and 3) are expensive operations.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
