Initial commit for thread-safe cb impl#24
Draft
enbnt wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Start of examples where concurrency and
thread safety concerns are introduced. This
is meant to be an example for a blog post
where we can run jmh benchmarks concurrently
against each solution to determine locking/synchronization
overhead.
The blog should also discuss how https://www.baeldung.com/java-ring-buffer thread-safe
producer consumer is not guaranteed - the access and comparison to both read & write vars is not an atomic operation, which leaves us with some tricky synchronization to ensure accurate results.
TODO: