[
https://issues.apache.org/jira/browse/BEAM-12203?focusedWorklogId=586877&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-586877
]
ASF GitHub Bot logged work on BEAM-12203:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 21/Apr/21 20:14
Start Date: 21/Apr/21 20:14
Worklog Time Spent: 10m
Work Description: scwhittle commented on pull request #14603:
URL: https://github.com/apache/beam/pull/14603#issuecomment-824328682
I think this is ready now. I verified direct executor is supported with
grpc and benchmarks improved.
--
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 586877)
Time Spent: 50m (was: 40m)
> Reduce thread context switches in BeamFnControlClient
> -----------------------------------------------------
>
> Key: BEAM-12203
> URL: https://issues.apache.org/jira/browse/BEAM-12203
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-harness
> Reporter: Sam Whittle
> Assignee: Sam Whittle
> Priority: P2
> Time Spent: 50m
> Remaining Estimate: 0h
>
> This class has a grpc observer that queues recieved messages on a
> LinkedBlockingQueue and then has a separate thread pulling from the the queue
> to add to an executor.
> Instead we could just add directly to the executor from the grpc stream, as
> the executor by default has an unbounded queue size (and there are comments
> indicating that a limited size executor can cause deadlocks otherwise)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
