>>>> While working on the BEAMJIT development I’ve been looking a lot at the luajit project and what Mike Pall has done both in the JIT but also in the interpreter. Inspired by this and some other ideas that we got from the BEAMJIT project we decided it was time to do a major overhaul of the way that the BEAM interpreter is created<p>As a long time Openresty (luajit) user, I have always feel a deep admiration for Mike Pall's work. After reading this, more so.
7.5% speed gain from BEAMJIT. 2.8x faster file ops because of dirty nifs support. Multiple poll sets. This is good stuff, I can't wait to benchmark it and play with it!
So is JIT coming to OTP 21 or not?<p>Because reading that post it’s confusing if they are releasing a JIT or simply making BEAM runtime improvements.<p>I ask because a JIT was scheduled for OTP 21 as noted here <a href="https://mobile.twitter.com/FrancescoC/status/872736686006046721" rel="nofollow">https://mobile.twitter.com/FrancescoC/status/872736686006046...</a>
> Also it is now possible to open device files using file:open<p>Anyone want to write a high-performance, highly distributed object store in a BEAM language?