Is there a difference between `<http://Dispatchers...
# coroutines
m
Is there a difference between 
<http://Dispatchers.IO|Dispatchers.IO>.limitedParalellism(100)
and
Dispatchers.Default.limitedParalellism(100)
?
j
During peak loads, the system may have up to 64 + 80 + 40 threads
Default has as threads as cores, so I think the total number should be different because it will not be 64 + X at least you have a 64 cores machine
j
with the guarantee that the effective parallelism of all views cannot exceed the actual parallelism of the original dispatcher.
This means the default dispatcher will not give you more parallelism than the number of cores. However the IO dispatcher could give you many threads
b
Behavior for these two is completely different. Limiting parallelism on Default will create a view with min(100, cores). On peak load the number of spawned threads won't exceed
cores
count. Limiting IO dispatcher has a special (elastic) behavior: it creates a view on IO's parent which is unbounded pool. So they will share threads if possible, but on peak load max number of spawned thread will be 100+64
m
Great, this is what I suspected, thanks 🙂