[
https://issues.apache.org/jira/browse/BEAM-7888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174678#comment-17174678
]
Beam JIRA Bot commented on BEAM-7888:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> 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: P2
> Labels: stale-P2
>
> 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.3.4#803005)
