[Threading] Threadpool, lifo semaphore #1190
Closed
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.
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
Checklist