You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2017/07/04 21:02:00 UTC

[jira] [Comment Edited] (FLINK-6359) Utilize Hierarchical Timing Wheels for performant timer

    [ https://issues.apache.org/jira/browse/FLINK-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15991975#comment-15991975 ] 

Ted Yu edited comment on FLINK-6359 at 7/4/17 9:01 PM:
-------------------------------------------------------

Interesting observations, Ben.


was (Author: yuzhihong@gmail.com):
Interesting observations, Ben .

> Utilize Hierarchical Timing Wheels for performant timer
> -------------------------------------------------------
>
>                 Key: FLINK-6359
>                 URL: https://issues.apache.org/jira/browse/FLINK-6359
>             Project: Flink
>          Issue Type: Improvement
>          Components: DataStream API, Local Runtime
>            Reporter: Ted Yu
>
> In this thread on mailing list:
> http://search-hadoop.com/m/Flink/VkLeQPmRa31hd5cw
> Gyula Fóra mentioned that timer deletion becomes performance bottleneck due to the usage of priority queue.
> Benjamin has an implementation for Hierarchical Timing Wheels (Apache License) :
> https://github.com/ben-manes/caffeine/blob/master/caffeine/src/main/java/com/github/benmanes/caffeine/cache/TimerWheel.java
> {code}
>  * A hierarchical timer wheel to add, remove, and fire expiration events in amortized O(1) time. The
>  * expiration events are deferred until the timer is advanced, which is performed as part of the
>  * cache's maintenance cycle.
> {code}
> We should consider porting the above over to facilitate performant timer.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)