4 ms·
> ECC memory ... remote management ... often considered necessary in a server environment Do note that an idiomatic Erlang cluster (where the distribution of t
by derefr 11y ago
> ECC memory ... remote management ... often considered necessary in a server environment
Do note that an idiomatic Erlang cluster (where the distribution of the system is used to achieve fault-tolerance, rather than for higher throughput) doesn't strictly need ECC memory (though, obviously, it wouldn't hurt.)
Also, such a system should be plenty manageable on its own—insofar as even an Erlang unikernel makes for a relatively ops-friendly system. There's little "remote management" can do that can't be done from an Erlang remsh. (Erlang even offers easy ways to expose e.g. SNMP MIBs.)
If you're talking about being able to re-image the system into being a completely non-Erlang system remotely, that might be hard—but a cluster-of-inexpensive-low-power-nodes setup like this only really has this one niche use-case to begin with, so I'm not sure what else you'd want to change it into.
- CJefferson 11y agoStupid question -- why wouldn't you need ECC? What does Erlang do special? I've found C programs occasionally returning incorrect results with non-ECC memory, as a memory location got corrupted. Does Erlang have some magic to avoid that?
- ansible 11y agoECC can prevent program crashes, but it can also prevent computation of incorrect results. Even if your memory is basically reliable, cosmic rays still can flip bits. As RAM sizes go up and up, your chances of seeing a memory error increase. My point, mainly, if we're talking about costs and power consumption, it isn't quite fair to compare server-grade hardware (which is more expensive than consumer-grade) with a RP2.
- jlouis 11y agoAn idiomatic Erlang cluster will have great benefit from ECC memory. The problem is that bit-flips can yield the wrong results for a while before the system crashes. And you may not be able to tolerate these wrong results.