You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Danny McCormick (Jira)" <ji...@apache.org> on 2022/06/04 12:44:00 UTC
[jira] [Commented] (BEAM-7888) Test Multi Process Direct Runner With Largish Data
[ https://issues.apache.org/jira/browse/BEAM-7888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17548022#comment-17548022 ]
Danny McCormick commented on BEAM-7888:
---------------------------------------
This issue has been migrated to https://github.com/apache/beam/issues/19678
> Test Multi Process Direct Runner With Largish Data
> --------------------------------------------------
>
> Key: BEAM-7888
> URL: https://issues.apache.org/jira/browse/BEAM-7888
> Project: Beam
> Issue Type: Task
> Components: sdk-py-core
> Reporter: Ahmet Altay
> Priority: P3
>
> Filing this as a tracker.
> We can test multiprocess runner with a largish amount of data to the extend that we can do this on Jenkins. This will serve 2 purposes:
> - Find out issues related to multi processing. It would be easier to find rare issues when running over non-trivial data.
> - Serve as a baseline (if not a benchmark) to understand the limits of the multiprocess runner.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)