partisan
partisan copied to clipboard
lasp-lang
High-performance, high-scalability distributed computing for the BEAM.
We need to improve Partisan concurrency so that we can capture the benefits of channels and parallelism per channel. At the moment there is * a single peer service manager...
The process might be constantly busy and never triggers a GC. Explore alternatives to ensure a GC, starting with hibernation, `fullsweep_after` spawn_opt.
At the moment the peer_service_manager will open and maintain one connection in each direction, that is when node A connects to node B it does not take into account that...
QUIC is secure by default and provides concurrent streams. This will imply changing: 1. TLS options. Right now we use TCP and we accept `tls :: boolean()` (`tls_server_options` and `tls_client_options`)....
# How to reproduce (Partisan v5.0.0 master) 1. Start two partisan nodes using `rebar3 shell` 2. Get the PidRef for the Erlang shell on node 2 e.g. ```erlang 1>partisan:self(). ```...
In V5 we have an updated node_spec ```erlang -type node_spec() :: #{ name := node(), listen_addrs := [listen_addr()], channels := #{channel() => channel_opts()} }. ``` `parallelism` is now a per...
It seems that the problem comes out from the fact, that OTP gracefully handles situation when `system_get_state/1` callback returns different value than `{ok, term()}`: https://github.com/erlang/otp/blob/412bff5196fc0ab88a61fe37ca30e5226fc7872d/lib/stdlib/src/sys.erl#L511-L512 Copying this code to `priv/otp/24/partisan_sys.erl`...
