I’m not expert here but I think most of that risk is mitigated these days since BEAM introduced Dirty Schedulers/Dirty NIFs for any NIFs that take over 1ms to execute… I think this isolates (or can isolate) their issues to only effecting other work on the same Dirty scheduler, aka other Dirty NIFs…

Few quick links:

https://www.erlang.org/doc/man/scheduler.html

https://medium.com/@jlouis666/erlang-dirty-scheduler-overhea...

https://bgmarx.com/2018/08/15/using-dirty-schedulers-with-ru...