[erlang-questions] Deprecation and removal of the non-smp emulator

Ryan Stewart zzantozz@REDACTED
Wed Apr 5 06:17:23 CEST 2017

If a big selling point of Erlang is how easy it makes concurrency (that's
how it seems to me), then spending a lot of effort on maintaining non-SMP
support seems silly. If you're not running SMP, then you're not really
doing what Erlang is excellent at, right? You could just as well be writing
C, Java, Lisp, or name your own language that doesn't have a great,
built-in concurrency model. I'm a relative noob, though, so what do I know?

On Tue, Apr 4, 2017 at 1:08 PM Tristan Sloughter <t@REDACTED> wrote:

Ah, ok, I thought the minimal mode meant no smp and there was a special
flag for erlc to turn on smp if you wanted it.

But either way, I agree improving startup time of smp enabled vm is

  Tristan Sloughter
  "I am not a crackpot" - Abe Simpson

On Tue, Apr 4, 2017, at 12:55 AM, Lukas Larsson wrote:

On Mon, Apr 3, 2017 at 6:34 PM, Tristan Sloughter <t@REDACTED> wrote:

First use case I thought of when I heard this news was 'erlc' itself :). It
disables smp by default, right?

erlc uses the following startup flags: "erl +A0 +sbtu -noinput -mode
minimal -boot start_clean"

So, it uses the smp emulator if available.

This gives a few milliseconds speedup in startup time when booting the VM
which is mostly a non-issue but nice for cli tools.

If startup time is important, I think the time would be better spent
optimizing the startup time of the smp-emulator, then to maintain the
non-smp emulators just for it's startup speed.

erlang-questions mailing list

erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20170405/f1087ac0/attachment.htm>

More information about the erlang-questions mailing list