beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-958) desiredNumWorkers in Dataflow is too low
Date Thu, 16 Feb 2017 15:39:41 GMT

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

ASF GitHub Bot commented on BEAM-958:
-------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/beam/pull/2009


> desiredNumWorkers in Dataflow is too low
> ----------------------------------------
>
>                 Key: BEAM-958
>                 URL: https://issues.apache.org/jira/browse/BEAM-958
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-dataflow
>    Affects Versions: Not applicable
>            Reporter: Raghu Angadi
>            Assignee: Raghu Angadi
>              Labels: backward-incompatible
>
> {{desiredNumWorkers}} in [UnboundedSource API|https://github.com/apache/incubator-beam/blob/v0.3.0-incubating-RC1/sdks/java/core/src/main/java/org/apache/beam/sdk/io/UnboundedSource.java#L69]
is a suggestion to a source about how many splits it should create. KafkaIO currently takes
this literally and only creates up to this many splits.
> The main draw back is that it is very low in Dataflow. It is calculated as 
>   * {{1 * maxNumWorkers}} if {{--maxNumWorkers}} is specified, otherwise
>   * {{3 * numWorkers}}.
> That implies there is only single reader per worker (which is usually a 4 core VM). That
can leave CPU under utilized on many pipelines.
> Even 3x in case of fixes number of workers seems low to me. 



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

Mime
View raw message