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]


Reply via email to