beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From María GH (JIRA) <j...@apache.org>
Subject [jira] [Comment Edited] (BEAM-2286) Improve mobile gaming example user experience
Date Sat, 13 May 2017 06:40:04 GMT

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

María GH edited comment on BEAM-2286 at 5/13/17 6:39 AM:
---------------------------------------------------------

I encountered the same issues described. Although, 1. is an understatement!--my Linux machine
completely froze for 10 minutes when using the default input. While the default input gets
changed, a note should be added to the documentation:
https://beam.apache.org/get-started/mobile-gaming-example/

Smaller datasets run without any problems.



was (Author: mariagh):
I encountered the same issues described. Although, 1. is an understatement!--my Linux machine
completely froze for 10 minutes when using the default input. While the default input gets
changed, a note should be added to the documentation:
https://beam.apache.org/get-started/mobile-gaming-example/

Smaller datasets run without any problems


> Improve mobile gaming example user experience
> ---------------------------------------------
>
>                 Key: BEAM-2286
>                 URL: https://issues.apache.org/jira/browse/BEAM-2286
>             Project: Beam
>          Issue Type: Improvement
>          Components: examples-java, sdk-py, website
>            Reporter: Vikas Kedigehalli
>            Assignee: Ahmet Altay
>            Priority: Minor
>
> Few things I noticed while running mobile gaming example that could be improved:
> 1. When running on direct runner the default input is too large (20G), so it seems as
though the pipeline is stuck without an progress updates or metrics.
> This could be improved by using a much smaller dataset by default.
> 2. Even when running on dataflow runner, with default worker settings and auto scaling,
it still takes more than 30 minutes to run. We could use a much smaller dataset here too.

> Also the documentation of these examples could be improved in both the code docstring
as well as beam quick start guide. 



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

Mime
View raw message