beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Weise (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-831) ParDo Chaining
Date Fri, 05 May 2017 16:05:04 GMT

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

Thomas Weise commented on BEAM-831:
-----------------------------------

There are changes needed on top of the original PR, I will submit a new PR. Also I see that
one of the unit tests does not terminate as expected when the chaining is enabled, that needs
to be looked into also.

> ParDo Chaining
> --------------
>
>                 Key: BEAM-831
>                 URL: https://issues.apache.org/jira/browse/BEAM-831
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-apex
>            Reporter: Thomas Weise
>            Assignee: Chinmay Kolhatkar
>             Fix For: First stable release
>
>
> Current state of Apex runner creates a plan that will place each operator in a separate
container (which would be processes when running on a YARN cluster). Often the ParDo operators
can be collocated in same thread or container. Use Apex affinity/stream locality attributes
for more efficient execution plan.  



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

Mime
View raw message