You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/11/08 22:38:00 UTC

[jira] [Work logged] (BEAM-8151) Allow the Python SDK to use many many threads

     [ https://issues.apache.org/jira/browse/BEAM-8151?focusedWorklogId=340788&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-340788 ]

ASF GitHub Bot logged work on BEAM-8151:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 08/Nov/19 22:37
            Start Date: 08/Nov/19 22:37
    Worklog Time Spent: 10m 
      Work Description: robertwb commented on issue #9477: [BEAM-8151, BEAM-7848] Up the max number of threads inside the SDK harness to a default of 10k
URL: https://github.com/apache/beam/pull/9477#issuecomment-552017665
 
 
   Could we perhaps get this in guarded by a flag so we can do performance testing while we wait for fixes and another release?
 
----------------------------------------------------------------
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:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 340788)
    Time Spent: 7h 50m  (was: 7h 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: 7h 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)