[erlang-questions] Non-blocking BEAM code loading?
Tue Nov 8 18:59:56 CET 2011
Would it help if we wrote some patches to make more of this work
happen before the block? Ideally there would be no block at all, but I
don't know enough about the internals to really make that happen.
Here's a branch (from R14B04) where I've moved most of the heavy
lifting (especially decoding the literal table) to before the block:
Most of the work is just putting the LoaderState on the heap instead
of the stack so it can be made part of the API without moving all of
the types out as well.
This helps in some tests I've done, but it seems that maybe just the
action of blocking and unblocking can introduce a significant pause
(~1 sec) under some circumstances.
2011/11/5 Björn-Egil Dahlberg <wallentin.dahlberg@REDACTED>:
> There is no other locking for code loading than blocking. This is an
> optimization of course since locking mechanism overhead is removed from the
> equation. Code loading is not used all that often in the normal cases
> besides startups and upgrades.
> That being said, there are plans to remove this "stop-the-world" strategy
> since it is blocking other strategies and optimizations. Also, we are well
> aware of that blocking does degrade performance when loading new modules and
> does not agree with our concurrency policy.
> I think we can lessen the time blocked in the current implementation but the
> blocking strategy should (and probably will) be removed. Nothing planned as
> of yet though.
> 2011/11/5 Bob Ippolito <bob@REDACTED>
>> We've found a bottleneck in some of our systems, when we load in large
>> new modules there is a noticeable pause (1+ seconds) that blocks all
>> of the schedulers. It looks like this is because the
>> erlang:load_binary/2 BIF blocks SMP before it does anything at all.
>> It would be a big win for us if more of this happened without blocking
>> the VM, there's a lot of busy work in loading a module that shouldn't
>> need any locking. For example, decompressing and decoding the literal
>> table is probably where our code spends almost all of its time.
>> There aren't a lot of comments for why it needs to lock the VM,
>> especially for the whole of load_binary. Are there any hidden gotchas
>> in here that I should know about before giving it a try? I'm unable to
>> find much where the block is actually necessary, but I am not very
>> familiar with the BEAM implementation yet.
>> I expect that the erts_export_consolidate, insert_new_code and
>> final_touch are really the only things that need so much
>> serialization, and maybe the set_default_trace_pattern… is there
>> anything big that I'm missing? It seems that breaking up
>> erts_load_module into two functions (one to do all the decoding
>> without the erts_smp_block_system(0), and the other to do the
>> integration work with the block) would be straightforward.
>> erlang-questions mailing list
More information about the erlang-questions