[
https://issues.apache.org/jira/browse/BEAM-8151?focusedWorklogId=343999&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-343999
]
ASF GitHub Bot logged work on BEAM-8151:
----------------------------------------
Author: ASF GitHub Bot
Created on: 15/Nov/19 05:47
Start Date: 15/Nov/19 05:47
Worklog Time Spent: 10m
Work Description: lukecwik commented on issue #10123: [BEAM-8151] Swap to
create SdkWorkers on demand when processing jobs
URL: https://github.com/apache/beam/pull/10123#issuecomment-554222266
R: @acrites
CC: @robertwb @aaltay
Favoring this PR if tests pass over the much worse #10091
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 343999)
Time Spent: 12h 50m (was: 12h 40m)
> Allow the Python SDK to use many many threads
> ---------------------------------------------
>
> Key: BEAM-8151
> URL: https://issues.apache.org/jira/browse/BEAM-8151
> Project: Beam
> Issue Type: Improvement
> Components: sdk-py-core, sdk-py-harness
> Reporter: Luke Cwik
> Assignee: Luke Cwik
> Priority: Major
> Time Spent: 12h 50m
> Remaining Estimate: 0h
>
> We need to use a thread pool which shrinks the number of active threads when
> they are not being used.
>
> This is to prevent any stuckness issues related to a runner scheduling more
> work items then there are "work" threads inside the SDK harness.
>
> By default the control plane should have all "requests" being processed in
> parallel and the runner is responsible for not overloading the SDK with too
> much work.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
