You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if a client is connected to a Supavisor node which does not own the pool there is communication with the pool processes which happen over Erlang distribution. With Erlang distribution there is only one TCP connection between nodes. On very busy clusters sometimes this can cause added latency.
We should instead create a TCP connection per client to the pool owner node to put client traffic on their own connections.
When a connection comes into a node which does not own the pool, a naive proxy should route traffic to pool owner node.
The text was updated successfully, but these errors were encountered:
Currently if a client is connected to a Supavisor node which does not own the pool there is communication with the pool processes which happen over Erlang distribution. With Erlang distribution there is only one TCP connection between nodes. On very busy clusters sometimes this can cause added latency.
We should instead create a TCP connection per client to the pool owner node to put client traffic on their own connections.
When a connection comes into a node which does not own the pool, a naive proxy should route traffic to pool owner node.
The text was updated successfully, but these errors were encountered: