3 ms·
Or you can just make a remote node out of your C/Java/Rust/whatever code and not worry too much about it crashing your Erlang system. It's not just crashing ei
by davidw 8y ago
Or you can just make a remote node out of your C/Java/Rust/whatever code and not worry too much about it crashing your Erlang system.
It's not just crashing either, it's taking a long time to execute a given function in the native code - that can also cause problems for the Erlang system running it.
- OvermindDL1 8y agoRemote nodes have overhead, however if you can handle that overhead then you definitely should use a remote node or Port over a NIF. However, NIF's taking a long time to run is not so much of an issue anymore now that the dirty NIF scheduler is enabled by default in the BEAM.