News for hackers. Stuff that matters.
Re:Membrane Framework – An Elixir framework for multimedia s... by andy_ppp on Friday July 27, 2018 @09:51AM (#17625925)
This looks very good and will be interesting to see how it scales in a large cluster - should be possible with it being written in Elixir to scale this out quite well. I'll also be interested to see how stable the NIFs are, I'd feel much more confident they weren't going to crash the VM if they were written in Rust.
Re:Membrane Framework – An Elixir framework for multimedia s... by mathek on Friday July 27, 2018 @01:04PM (#17627398)
Concerning NIFs, it is entirely possible to write Membrane elements using NIFs in Rust ;) The reason why current ones are written in pure C is that they mostly consist of calls to existing libraries, also in C. We've experimented with using Rust, but we ended up with most part of our code being unsafe calls to library functions, providing more boilerplate than profits. If we are to create a considerable big native part of Membrane, we will definitely consider using Rust.
Re:Membrane Framework – An Elixir framework for multimedia s... by sidkshatriya on Friday July 27, 2018 @10:19AM (#17626130)
Good point. Whats the point of using the Erlang VM if your NIF could bring down the whole VM. How is this different from using any other language like Go then to implement this platform?

The approach confuses me because there is so much praise for the Erlang VM but to get all its benefits of the Erlang VM they need to use ports. (Which they confess is going to be slower).

Re:Membrane Framework – An Elixir framework for multimedia s... by mspanc on Friday July 27, 2018 @12:14PM (#17627033)
We're thinking about adding an abstraction layer over C code that will allow to switch between NIF and port backends. Ports have their limitations so you won't be able to use them e.g. for passing GPU buffers but they will do the job for many other cases.

Anyway even with NIFs we delegate to them only code that cannot be written in Elixir or it really makes no sense to keep it in Elixir e.g. in performance reasons. Even if 30% of the framework will be in C it's way easier to manage 30% of C code than 100% of C code.

Moreover, all the hard stuff, such as parallelism, being able to inspect running state of the VM, ability to spread app over cluster, I/O scalability, being multiplatform etc. comes out of the box with BEAM VM. There are many things that are give the point of using Erlang VM even if part of the code is in C and is potentially dangerous.

Re:Membrane Framework – An Elixir framework for multimedia s... by sidkshatriya on Friday July 27, 2018 @01:32PM (#17627623)
Thanks for your reply. The BEAM VM is amazing (and I'm a fan of Elixir) but I'm trying to see what benefit you're getting out of BEAM if you're using NIFs. Because the moment you use NIFs then your VM can crash (without recourse to the various recovery mechanisms of the BEAM) just like, say, a Golang executable.

If you used Golang you would also get parallelism, I/O scalablity, multiplaform capability... all the things you list as advantages for BEAM. The only thing that BEAM is giving you "extra" vs, say, Golang is the ability to spread your app over a cluster easily. But again, I'm sure you can achieve that with some sort of a load distributer if you used Golang on multiple machines. Also with Golang it is easy to do CPU intensive tasks because its "closer" to the metal. So I guess what I'm saying is that for your specific use case (that involves a lot of media related CPU intensive work like video/audio processing) I wonder if the BEAM VM will give you that many advantages. With Golang in this case I think you can get the scalability, reliability as your current setup with one big advantage: better performance. But this is just my ~5 min view of the subject...

Re:Membrane Framework – An Elixir framework for multimedia s... by mspanc on Saturday July 28, 2018 @10:05AM (#17633214)
Hello,

I evaluated Go at the very beginning and after making proof of concept I decided to stay with Elixir.

One of the reasons was that Go has garbage collector that can "stop the world" which is really not acceptable in some low-latency applications. BEAM VM does GC per erlang process.

Secondly, significant chunk of such framework is about interoperability with C as there're tons of libraries we're going to wrap around. cgo essentially requires developer to reimplement in definition of every single structure and function we're going to ever use. It's a massive overhead (not in sense of computational overhead but time spent).

NIFs are way simpler, there just regular C code you can link with libraries without any overhead. Remember that in such framework we're going to do quite o lot of pointer arithmetic and having plain C code is a huge advantage.

All that together allows us to have greater flexibility on how to design C layer. cgo binds us to a particular solution that is not really well designed. With Elixir we can even write C code in Rust as was suggested in another comment.

Please remind that what is really computationally expensive will be often written in C/C++ anyway or done by GPU. Framework does not add that much overhead in macro scale, it's often just a glue and abstraction layer.

And finally, if you read our goals, we clearly state that if we have to make a tradeoff, we put reliability over performance. The motivation to start Membrane was that while designing broadcasting systems we struggled to achieve true 24/7 availability with existing frameworks. You can't compare 20+ years of Erlang development in this area with Go. I mean both maturity of the VM, as well as battle-tested design patterns, built-in supervision, hot upgrades and so on.

Go is cool, trendy and has very loyal user base but it's not free of caveats.

Re:Membrane Framework – An Elixir framework for multimedia s... by sidkshatriya on Monday July 30, 2018 @09:50AM (#17644386)
Thanks again for your detailed response. I was curious to know why you choose BEAM because Golang vs BEAM is often a genuinely confusing option. Thanks for your insights on NIFs.

Additionally, as someone in this thread has already pointed out, it is also a matter of taste and preference on choosing Elixir over Golang.

A point about Elixir macros -- I think you will find that while macros increase your productivity, they make debugging the code a bit more difficult.

Wish your project best of luck. The website looks slick!

Re:Membrane Framework – An Elixir framework for multimedia s... by mspanc on Saturday July 28, 2018 @12:14PM (#17633743)
Moreover, while one can say that all of these differences are not that important, there're clear differences in the language: Elixir has metaprogramming, you can easily achieve a lot of stuff in the compile time via macros, go lacks generics and good versioning and interface for plugins most probably would have needed to be written using reflections. Elixir looks just way more modern.
Re:Membrane Framework – An Elixir framework for multimedia s... by elcritch on Friday July 27, 2018 @06:15PM (#17629896)
Not the OP, but it strikes me that at some level it becomes a personal preference alongside the technical benefits. Though regarding error handling and NIFs, Erlang/OTP manages high reliability not just through local OTP mechanisms, but also through the clustering. It’s a fundamental part of the OTP ethos and something that would need to be “bolted on” in Go. That and the introspection tools are pretty great!
Re:Membrane Framework – An Elixir framework for multimedia s... by nailer on Friday July 27, 2018 @10:23AM (#17626156)
What's a NIF in this context?
Re:Membrane Framework – An Elixir framework for multimedia s... by andy_ppp on Friday July 27, 2018 @10:27AM (#17626187)
Native Implementation Functions - http://erlang.org/doc/tutorial/nif.html - Erlang/Elixir would not be performant enough to generate realtime video/audio encoding.

It's possible to make them crash the VM if they leak memory or don't prempt when asked. In Rust you can make better guarantees about your code and there is this that allows you to write them in Rust: https://github.com/hansihe/rustler

Re:Membrane Framework – An Elixir framework for multimedia s... by mspanc on Friday July 27, 2018 @12:17PM (#17627054)
Nice hint, we'll definitely take this under consideration!
Re:Membrane Framework – An Elixir framework for multimedia s... by sjtgraham on Friday July 27, 2018 @10:34AM (#17626242)
Solution: NIFs on remote nodes.
Re:Membrane Framework – An Elixir framework for multimedia s... by dqv on Friday July 27, 2018 @04:56PM (#17629327)
Like a C node? Or a node on another VM?