Implement BeamAsm – A JIT for Erlang/OTP

This was posted by one of our members via one of our automated news source trackers. If you feel this thread could be in a better category or could include better tags and you are at Trust Level 3 or higher, please feel free to move/edit it :+1:

4 Likes

It’s amazing! But it says that Erlang will use more memory after this, and it already used too much memory comparing to Go or Node, or even Ruby.
(Of course BEAM does a lot of more work which causes the higher use of memory).

1 Like

When would that be an issue DG?

1 Like

It may become an issue when the amount of memory available is small, like in Heroku, Gigalixir or some of AWS/GCP instances.

1 Like

I thought that’s what you might have meant :slight_smile:

Personally I don’t think that is a worry for the target-users of Elixir/Erlang - those who need massive scale for very busy/large projects. Ram gets cheaper over time too so I’m sure more ram will be reflected in cloud services at the same price point sooner or later :smiley:

1 Like