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 the topology unbuild is implemented as a sequential node destruction.
Node destruction is implemented as a destroy, remove, and wait sequence.
We can speed up the unbuild by calling the destroy and remove of all nodes first, then wait until all of them are removed.
This can implement this as threads (consider GIL), or refactor the workflow. We also need to consider the the hooks interfaces defined by the core framework.
The text was updated successfully, but these errors were encountered:
Currently the topology unbuild is implemented as a sequential node destruction.
Node destruction is implemented as a destroy, remove, and wait sequence.
We can speed up the unbuild by calling the destroy and remove of all nodes first, then wait until all of them are removed.
This can implement this as threads (consider GIL), or refactor the workflow. We also need to consider the the hooks interfaces defined by the core framework.
The text was updated successfully, but these errors were encountered: