On Mon, Aug 1, 2016 at 6:38 AM, 'Sugu Sougoumarane' via golang-nuts < golang-nuts@googlegroups.com> wrote:
> Instead, if you ran something like 10x instances of the same program, > you'll end up using the same resources, but will get much better > performance, and your code will be much simpler. This is the Erlang solution to the problem. For each proxy-request, run a server, in isolation. You don't run one process handling a million requests. You run a million processes each handling one request. It is literally what happens in the VM internals as well. Each process has its own heap and can be GC'ed in isolation. Of course this requires you copy data into the process for communication, and this is the secret of the Erlang VM. In fact, everyone else is doing it wrong, often citing odd claims of "efficiency" as a reason. You end up having to build rather complex GC schemes, whereas Erlang just uses a tried and true 2-space copying collection by Cheney. -- J. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
