[
https://issues.apache.org/jira/browse/BEAM-11730?focusedWorklogId=558384&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-558384
]
ASF GitHub Bot logged work on BEAM-11730:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 26/Feb/21 03:47
Start Date: 26/Feb/21 03:47
Worklog Time Spent: 10m
Work Description: reuvenlax merged pull request #13878:
URL: https://github.com/apache/beam/pull/13878
----------------------------------------------------------------
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: 558384)
Time Spent: 2h 10m (was: 2h)
> Reduce context switches for dataflow streaming appliance getdata reads
> ----------------------------------------------------------------------
>
> Key: BEAM-11730
> URL: https://issues.apache.org/jira/browse/BEAM-11730
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow
> Reporter: Sam Whittle
> Assignee: Sam Whittle
> Priority: P2
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Currently reads are batched and issued from a separate thread pool of reading
> threads. However in the case that there is not read queuing due to the max #
> of parallel requests, switching threads is unnecessary and adds additional
> context swithing overhead.
> In a benchmark I observed 5% cpu spent on LockSupport.park which some
> googling indicates is due to context switching.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
