options for high-throughput connections between nodes

[Karl Nilsson]

Osiris is quite a different type of thing to the other ones in your list in
that it will always first write terms to disk and only then replicate them
(over TCP). That said it could do a decent replication job if you want a
local buffer to decouple the production of terms from the replication part.
Osiris does still need a dist erl connection for coordination messages and
you'd have to modify the quorum commit semantics to fit your use case (e.g.
a "leader" member on the production side and a "replica" member on the
other side).

Cheers
Karl

On Fri, 1 Apr 2022 at 11:01, Dave Cottlehuber <dch@REDACTED> wrote:

> I'm investigating how to maximise pushing mostly loosely ordered erlang
> terms (via `term_to_binary/1` and friends) between a mesh of erlang nodes.
>
> A single TCP stream isn't sufficient, so I'm expecting using either UDP or
> multiple TCP streams, to push up throughput. I don't expect the usual
> erlang distribution protocol to be suitable, because of the risk of
> congestion and head-of-line blocking of distribution-related traffic.
>
> Assume LFN scenario (Long Fat Pipes), up to 3-10GiB/s bandwith, usual
> inter-continental latency as default. No numbers yet, just "as much as
> possible / closest to theoretical maximum bandwidth".
>
> - zeromq: https://github.com/zeromq/chumak |
> https://github.com/zeromq/erlzmq2 | https://github.com/lukaszsamson/erlzmq
> - osiris: https://github.com/rabbitmq/osiris
> - nanomsg: https://github.com/basho/enm
> - https://www.erlang.org/doc/man/gen_sctp.html
>
> Has anybody other suggestions to add to the list?
>
> thanks
> Dave
>


-- 
*Karl Nilsson*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20220401/6de4f80d/attachment.htm>