[erlang-questions] Troubling gen_tcp.send/3 performance

[Matthew Shapiro]

In regards to your architecture response, Each process is responsible to
sending and receiving to only one TCP socket as each process represents a
single TCP connection.

In terms of RTMP, I run a streaming service company so I'm pretty aware of
whats going on.  RTMP may be dead for viewing but it most certainly is not
a dead protocol for live video ingestion and distribution, and thus there
are still very valid reasons for RTMP support in a media server.

I have much grander plans for this than just RTMP ingest/playback but it's
a pointless effort to start working on other things like creating an HLS
feed from an RTMP feed if I can't even get regular RTMP playback to work
properly yet.

On Sun, Dec 4, 2016 at 2:24 PM, Max Lapshin <max.lapshin@REDACTED> wrote:

> The first question is your architecture.
>
> If you want to make gen_tcp:send to different sockets from one process,
> then you have wrong architecture and need to change all this.
>
> Flussonic has rtmp server inside and after some performance optimizations
> (all are high-level, algorithmic) it can send 1-3 gbit/s via rtmp.  But it
> is the top.  RTMP is a dead protocol, you are just wasting your time on it
> because till the end of 2017 it will be disabled in almost all browsers.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20161204/9f7ce144/attachment.htm>