[
https://issues.apache.org/jira/browse/BEAM-11730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Whittle updated BEAM-11730:
-------------------------------
Resolution: Fixed
Status: Resolved (was: Open)
> 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)
