Skip to content
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

The thread pool's global queue doesn't scale well on machines with a large processor count #67845

Closed
kouvel opened this issue Apr 11, 2022 · 1 comment · Fixed by #69386
Closed

Comments

@kouvel
Copy link
Member

kouvel commented Apr 11, 2022

The time spent spin-waiting in the ConcurrentQueue increases as the processor count increases and worker threads spend less time processing work. May consider queuing work more locally, introducing multiple queues, or other techniques.

@kouvel kouvel added this to the 7.0.0 milestone Apr 11, 2022
@ghost
Copy link

ghost commented Apr 11, 2022

Tagging subscribers to this area: @mangod9
See info in area-owners.md if you want to be subscribed.

Issue Details

The time spent spin-waiting in the ConcurrentQueue increases as the processor count increases and worker threads spend less time processing work. May consider queuing work more locally, introducing multiple queues, or other techniques.

Author: kouvel
Assignees: -
Labels:

area-System.Threading

Milestone: 7.0.0

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Apr 11, 2022
@kouvel kouvel removed the untriaged New issue has not been triaged by the area owner label Apr 11, 2022
@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label May 18, 2022
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Jun 7, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Jul 7, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant