-
Notifications
You must be signed in to change notification settings - Fork 144
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
MessagePool Greedy Message Selection #856
Conversation
…o ec2/mpool-selection
/// Like head_change, except it doesnt change the state of the MessagePool. | ||
/// It simulates a head change call. | ||
pub async fn run_head_change<T>( | ||
api: &RwLock<T>, |
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.
Can definitely come in another PR, but it's really weird and probably really slow to have all interactions with the provider be behind a mutex, even for operations not relating to each other. It doesn't make sense that any of the functions require a mutable reference, so requiring an exclusive lock is definitely inefficient
Summary of changes
Changes introduced in this pull request:
Reference issue to close (if applicable)
Closes #709
Other information and links