You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes, you want to isolate a workload from the main thread pool. For example, when you start a Parallel loop in a fresh process, this sometimes immediately exhausts the thread pool. This crowds out other work and even stops timers from firing until the pool responds.
I know of no built-in way to achieve this.
I use the WorkStealingTaskScheduler from the old ParallelExtensionsExtras for this purpose. The library is long abandoned and not supported.
It should be possible to set the thread priority (maybe through a callback that notified user code when a thread was created so that it can be configured arbitrarily).
The text was updated successfully, but these errors were encountered:
A custom thread pool is out-of-scope for this (async-oriented) library.
Generally, most devs handle this by boosting the minimum thread pool count and then using ConcurrentExclusiveSchedulerPair (which migrated into the BCL from ParallelExtensionsExtras). Is there a reason that approach wouldn't work for you?
Sometimes, you want to isolate a workload from the main thread pool. For example, when you start a
Parallel
loop in a fresh process, this sometimes immediately exhausts the thread pool. This crowds out other work and even stops timers from firing until the pool responds.I know of no built-in way to achieve this.
I use the
WorkStealingTaskScheduler
from the oldParallelExtensionsExtras
for this purpose. The library is long abandoned and not supported.It should be possible to set the thread priority (maybe through a callback that notified user code when a thread was created so that it can be configured arbitrarily).
The text was updated successfully, but these errors were encountered: