cats-effect
cats-effect copied to clipboard
Add parallelismFactorHint to Spawn[F]
Someone asked in Discord if there is a way to ask the CE runtime how many CPUs/compute threads it has access to, so that they can set parallelism factors appropriately. It's available in IOApp as computeWorkerThreadCount but this is specific to IOApp and therefore not easily usable from all the places in c.e.std that could benefit from it.
Once it's added to Spawn, new methods or overrides should be added setting default parallelism factors accordingly. For example, in addition to Random.scalaUtilRandomN, there should be a variant that sets N to the computeWorkerThreadCount.
There was some discussion of this in Discord, which I will attempt to summarize:
- Daniel originally suggested it as
concurrencyFactorHint: Option[Int](orparallelismFactorHint: Option[Int]in the interest of consistent terminology). - Arman suggested avoiding the
Optionbox by defaulting to 0, to which Daniel "didn't totally object," because "technically anything ≤ 0 is semantically invalid anyway" and "if we go with 0 as the default then the fallback could be to tap the runtime anyway" - There was also some discussion about whether this should be
F[Int]to reflect the reality that the number can change in some circumstances, but that opens up quite a rabbit hole, so it may not be worth it? IfF[Int]is used, should there be some kind of notification protocol to let data structures optimized for a given value rebalance themselves if the value changes?
For Spawn[IO], would this return availableProcessors() or the size of the WSTP? (Because the two is not necessarily the same.)
The latter. The idea here is that the hint would help the user build downstream data structures which have striping strategies which are sensitive to the maximum true parallelism. Dispatcher and Random are two decent examples within std.
In that case, I can't really see how to implement it as a : Int... return the size of what WSTP? There might not even exist one. (While if we're doing it as a : F[Int], we'd use the one we're running on. Although, that still could be a non-WSTP Executor.)
This is a good point. I think this probably needs to be F[Int], and we should just blindly use the runtime that we're running on rather than trying to account for evalOn.