My OTP 21 Highlights

#1

Post by mischov » Wed, May 02, 2018, 5:00 PM UTC

My OTP 21 Highlights
blog.erlang.org

Re: My OTP 21 Highlights

#2

Post by dnautics » Wed, May 02, 2018, 8:02 PM UTC

> Also it is now possible to open device files using file:open

Anyone want to write a high-performance, highly distributed object store in a BEAM language?

Re: My OTP 21 Highlights

#3

Post by misterbowfinger » Wed, May 02, 2018, 8:09 PM UTC

dnautics wrote: post #2

> Also it is now possible to open device files using file:open Anyone want to write a high-performance, highly distributed object store in a BEAM language?

i got u

Re: My OTP 21 Highlights

#4

Post by ghayes » Wed, May 02, 2018, 9:10 PM UTC

It's great to see the team continuing to work toward better performance. Each improvement can help every application built on BEAM.

Re: My OTP 21 Highlights

#5

Post by lliamander » Wed, May 02, 2018, 9:11 PM UTC

dnautics wrote: post #2

> Also it is now possible to open device files using file:open Anyone want to write a high-performance, highly distributed object store in a BEAM language?

Maybe something based on this paper: https://blog.acolyer.org/2018/03/27/anna-a-kvs-for-any-scale... ?

Re: My OTP 21 Highlights

#6

Post by Immortalin » Wed, May 02, 2018, 9:26 PM UTC

dnautics wrote: post #2

> Also it is now possible to open device files using file:open Anyone want to write a high-performance, highly distributed object store in a BEAM language?

CouchDB?

Re: My OTP 21 Highlights

#7

Post by dnautics » Wed, May 02, 2018, 9:53 PM UTC

Immortalin wrote: post #6

dnautics wrote: post #2

> Also it is now possible to open device files using file:open Anyone want to write a high-performance, highly distributed object store in a BEAM language?

CouchDB?

binaries, not structured objects. Redundancy via erasure coding, etc.

Re: My OTP 21 Highlights

#8

Post by alberth » Wed, May 02, 2018, 10:36 PM UTC

So is JIT coming to OTP 21 or not?

Because reading that post it’s confusing if they are releasing a JIT or simply making BEAM runtime improvements.

I ask because a JIT was scheduled for OTP 21 as noted here https://mobile.twitter.com/FrancescoC/status/872736686006046...

Re: My OTP 21 Highlights

#9

Post by mischov » Wed, May 02, 2018, 11:28 PM UTC

alberth wrote: post #8

So is JIT coming to OTP 21 or not? Because reading that post it’s confusing if they are releasing a JIT or simply making BEAM runtime improvements. I ask because a JIT was scheduled for OTP 21 as noted here https://mobile.twitter.com/FrancescoC/status/872736686006046...

I think it's part of the "and beyond" in that picture, and not coming in OTP 21.

This video also supports that guess: https://youtu.be/hHhm0bfdj-4?t=10m14s

Re: My OTP 21 Highlights

#10

Post by macintux » Thu, May 03, 2018, 12:57 AM UTC

dnautics wrote: post #2

> Also it is now possible to open device files using file:open Anyone want to write a high-performance, highly distributed object store in a BEAM language?

Based on my time at Basho observing and assisting with the development of Riak[1], I don't think you'll get the performance you want from built-in I/O, even with the new dirty scheduler support.

We (well, primarily Matthew Von-Maszewski) spent countless hours optimizing LevelDB as the most performant backend for most use cases.

You'd be much better off building atop Riak than starting your own object store from scratch.

[1]: Most active Riak development today is courtesy the NHS - https://github.com/nhs-riak/riak