[erlang-questions] Why is erlc so quick to start?

[Tuncer Ayaz]

On Mon, Jan 5, 2015 at 6:12 PM, Bjorn-Egil Dahlberg wrote:
> As I mentioned in a previous thread, the start time of escript and
> erl is to an high degree influenced by the all the modules that
> needs to be loaded.

More modules, bigger modules (line info).

> This is also why +A0 has an impact.

Just to be clear, you aren't saying +A1 implies loading extra modules,
are you?

> I have to caution you to use +A0 though. Short-circuiting file
> operation by using no async-threads may be hazardous to your system.
> In most cases it is just fine to use it but this is very
> unpredictable. The schedulers can become very unhappy.
>
> We can change the default arguments to escript to mitigate this, for
> instance:
> erlang:master...egil/default-escript-arguments

Isn't +sbtu already the default?

> As for something more rigorous: Dizzy had a proposal of creating
> escripts with a beam-binary with erlang-archives appended to it. I
> don't know how far he got but with this. Something like that might
> go a long way to speed things up.

Never heard of that. Care to elaborate?

The escript archives we create currently are already a header followed
by a zip archive, but IIRC concatenating beam files also works, though
I never tried it and just recall the escript loader bits related to
it.