Thanks! That is my current approach and it works quite well with the only caveat of having to “guess” the proper pool size for each environment.
The “normal” schedulers context switch very frequently but dirty_cpu schedulers might not do that (depending on the NIF implementation) so I am trying to be safe here and not ever allowing it to reach 100%.
