[
https://issues.apache.org/jira/browse/BEAM-13015?focusedWorklogId=744158&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-744158
]
ASF GitHub Bot logged work on BEAM-13015:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 18/Mar/22 15:10
Start Date: 18/Mar/22 15:10
Worklog Time Spent: 10m
Work Description: scwhittle edited a comment on pull request #17122:
URL: https://github.com/apache/beam/pull/17122#issuecomment-1072482157
R: @lukecwik Is this what you were thinking to fix the excessive isReady
cpu? I didn't just use a synchronized block so it would be fair. I kept the
existing syncronization instead of just using the new lock since I wasn't sure
if we required that synchronization on the observer for safe usage of the
underlying observer elsewhere.
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 744158)
Time Spent: 69h 10m (was: 69h)
> Optimize Java SDK harness
> -------------------------
>
> Key: BEAM-13015
> URL: https://issues.apache.org/jira/browse/BEAM-13015
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-harness
> Reporter: Luke Cwik
> Assignee: Luke Cwik
> Priority: P2
> Time Spent: 69h 10m
> Remaining Estimate: 0h
>
> Use profiling tools to remove bundle processing overhead in the SDK harness.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
