Reentrant lock benchmark improvements #3469
Closed
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
|
@unclebob418 What do we need to do to get this over the finish line? |
|
@adamgfraser sorry, got a bit side tracked with zio-sql. Here was my last comment from the previous PR. Do you think this is a reasonable idea? Ideally we actually use the reentry capabilities at least to the extent that java supports them to do this (e.g. read first, then upgrade to write for the writers) |
|
@robmwalsh I know this was an experiment and WIP, so I will close for now, but feel free to re-open anytime! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
follow on from #3099 for benchmark improvements
and no, I'm not going to leave it at 1 iteration :)