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

[Threading] Threadpool, lifo semaphore #1190

Closed
wants to merge 2 commits into from

Conversation

Eideren
Copy link
Collaborator

@Eideren Eideren commented Nov 17, 2021

PR Details

Now that .Net6 uses their fully managed threadpool by default we can hook into their lifo semaphore which improves performances slightly.
I did benchmark their System.Threading.ThreadPool.UnsafeQueueUserWorkItem again under net6 and ours still performed better, so still no reason to migrate to dotnet's threadpool.

Types of changes

  • Docs change / refactoring / dependency upgrade
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist

  • My change requires a change to the documentation.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@Eideren
Copy link
Collaborator Author

Eideren commented Jan 7, 2024

Implemented through #2083

@Eideren Eideren deleted the tp_lifosem branch January 7, 2024 18:28
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.

1 participant