beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Halperin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-690) Backoff in the DirectRunner Monitor if no work is Available
Date Mon, 03 Apr 2017 17:17:41 GMT

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

Daniel Halperin commented on BEAM-690:
--------------------------------------

[~tgroh] any update here? Should this block first stable release – DirectRunner CPU usage
has caused us a number of testing issues.

> Backoff in the DirectRunner Monitor if no work is Available
> -----------------------------------------------------------
>
>                 Key: BEAM-690
>                 URL: https://issues.apache.org/jira/browse/BEAM-690
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-direct
>            Reporter: Thomas Groh
>             Fix For: First stable release
>
>
> When a Pipeline has no elements available to process, the Monitor Runnable will be repeatedly
scheduled. Given that there is no work to be done, this will loop over the steps in the transform
looking for timers, and prompt the sources to perform additional work, even though there is
no work to be done. This consumes the entirety of a single core.
> Add a bounded backoff to rescheduling the monitor runnable if no work has been done since
it last ran. This will reduce resource consumption on low-throughput Pipelines.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message