Skip to content

Increment WorkQueue.blockingTasksInBuffer only after capacity check #3569

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

Merged
merged 1 commit into from
Jan 16, 2023

Conversation

qwwdfsad
Copy link
Member

@qwwdfsad qwwdfsad commented Jan 3, 2023

Otherwise, it is possible to leave dangling blockingTasksInBuffer increment that will never be decremented back, leading to unnecessary full-scans on any attempt to steal only blocking task. This change does not have a corresponding unit-test because it fixes the performance regression that is not observable semantically

@qwwdfsad qwwdfsad requested a review from dkhalanskyjb January 3, 2023 11:04
Base automatically changed from scheduler-improvement to develop January 16, 2023 16:08
Otherwise, it is possible to leave dangling blockingTasksInBuffer increment that will never be decremented back, leading to unnecessary full-scans on any attempt to steal only blocking task.
This change does not have a corresponding unit-test because it fixes the performance regression that is not observable semantically
@qwwdfsad qwwdfsad force-pushed the fix-blocking-counter-race branch from b37d334 to 54c6de3 Compare January 16, 2023 16:10
@qwwdfsad qwwdfsad merged commit 4102f90 into develop Jan 16, 2023
@qwwdfsad qwwdfsad deleted the fix-blocking-counter-race branch January 16, 2023 16:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants