-
Notifications
You must be signed in to change notification settings - Fork 632
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: clean up busy waiting in prefetcher blocking get #8215
Merged
near-bulldozer
merged 14 commits into
near:master
from
pugachAG:prefetcher-blocking-get
Dec 22, 2022
Merged
Changes from 2 commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
f55cded
Initial implementation
pugachAG 0627abd
Minor updates
pugachAG 3b9b27a
Avoid passing mutex guard to notify_slots_update
pugachAG 446b32e
Use explicit guard variable
pugachAG cebbd82
Introduce Monitor
pugachAG 53412e7
Remove tmp guard
pugachAG f861cd7
fmt
pugachAG 8e4a161
Reorder use
pugachAG cb59478
from_micros -> from_millis
pugachAG 2ec4546
Simplify test
pugachAG ceec97c
Use prefetch_staging_area2 async
pugachAG 965a75b
Fix comment
pugachAG 04cd64c
Fix another comment
pugachAG 9fc336f
Merge branch 'master' into prefetcher-blocking-get
pugachAG File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this actually a right thing to do? My intuition is that we want to notify first and unlock after, so that the mutex is fairly distributed along all the waiters on the condvar. If it is unlocked before the notification, some other waiter that’s not in a condvar might grab the mutex, leading to all the condvar waiters block immediately after them being notified (a-la thundering herd?)
The standard library doc examples seem to corroborate with my understanding…
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With unlocking the mutex before notifying I wanted to address exactly that issue (see stackoverflow). In this particular case I don't think it would matter since this is definitely not a performance bottleneck. I will change this to match the example
Condvar
usage from the docs to avoid trying to be "unnecessarly smart" here :)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FWIW I raised a question about this upstream. They have some interesting insights :)