On each connection add/delete/established event from a peer mesh router broadcasts topology updates to the peers. In fully connected topology broadcast would be to the all nodes in mesh.
A received topolgy gossip is further relayed to the peers if its a new update. While this should not be a concern in a stable topology it can be problematic in some use-cases.
For e.g.
when some one deploys a weave-net deamonset in N node cluster it can result in each node connecting to other nodes. Hence concurrent topology updates can get it in the order of n^2 in the cluster
in auto-scaling group's nodes can get added/deleted that can result in high topology updates
Considering #114, #115 which resuts in high cpu usage, combination chatty topology gossip results in cascading effect.
As number of peers in the mesh increases it significantly impacts scalability.
Following metrics were gathered with instrumented mesh on 150 node kubernetes cluster running weave-net using mesh. rx gossip broadcast are received topology gossip per second.
On each connection add/delete/established event from a peer mesh router broadcasts topology updates to the peers. In fully connected topology broadcast would be to the all nodes in mesh.
A received topolgy gossip is further relayed to the peers if its a new update. While this should not be a concern in a stable topology it can be problematic in some use-cases.
For e.g.
Considering #114, #115 which resuts in high cpu usage, combination chatty topology gossip results in cascading effect.
As number of peers in the mesh increases it significantly impacts scalability.
Following metrics were gathered with instrumented mesh on 150 node kubernetes cluster running weave-net using mesh.
rx gossip broadcast
are received topology gossip per second.