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
Get meshnet topology spec for each node, in sequence
Review each spec to ensure peer node name consists of actual pod name for a given peer node (since node != pod)
Create meshnet CR for each spec, in sequence
Delegate node creation to vendor specific implementation, in sequence
Loop through all nodes and call vendor specific implementation to ensure the corresponding node is ready, in sequence
4. and 5. is specifically a problem because operation on a given node blocks the operation on subsequent nodes. This causes significant slowness as we increase the number of nodes in a topology.
It should be feasible to enhance them to operate concurrently (one goroutine for each node).
There's also the opportunity to make 1. and 3. concurrent but I do not have enough data to confirm that it causes significant slowness.
The text was updated successfully, but these errors were encountered:
Here's a rough flow of sequence of operations:
pod name
for a given peer node (since node != pod)4.
and5.
is specifically a problem because operation on a given node blocks the operation on subsequent nodes. This causes significant slowness as we increase the number of nodes in a topology.It should be feasible to enhance them to operate concurrently (one goroutine for each node).
There's also the opportunity to make
1.
and3.
concurrent but I do not have enough data to confirm that it causes significant slowness.The text was updated successfully, but these errors were encountered: