Recently, I encountered some performance issues when using libavoid (js/wasm version) for automatic route connection. I would like to seek some experienced advice.
The current usage scenario involves a large number of elements and connections on the page, along with frequent position changes (such as dragging and real-time updates). In this scenario, there is noticeable lag every time processTransaction() is called for path calculation.
I would like to know about:
In high-frequency change scenarios, are there any recommended optimization methods for using libavoid? For example, is it recommended to reduce the frequency of transaction calls, or adopt some kind of batch processing strategy?
Is it possible to perform incremental calculation only on the "affected local connections" instead of calling processTransaction() in full every time?
In scenarios with large element/connection scales (such as hundreds of nodes and thousands of connections), are there any parameter configurations or usage patterns that can significantly improve performance?
If libavoid itself is not quite suitable for high real-time scenarios, are there any lighter or more suitable alternatives for real-time interaction in the community?
Looking forward to your reply. Thank you
Recently, I encountered some performance issues when using libavoid (js/wasm version) for automatic route connection. I would like to seek some experienced advice.
The current usage scenario involves a large number of elements and connections on the page, along with frequent position changes (such as dragging and real-time updates). In this scenario, there is noticeable lag every time processTransaction() is called for path calculation.
I would like to know about:
In high-frequency change scenarios, are there any recommended optimization methods for using libavoid? For example, is it recommended to reduce the frequency of transaction calls, or adopt some kind of batch processing strategy?
Is it possible to perform incremental calculation only on the "affected local connections" instead of calling processTransaction() in full every time?
In scenarios with large element/connection scales (such as hundreds of nodes and thousands of connections), are there any parameter configurations or usage patterns that can significantly improve performance?
If libavoid itself is not quite suitable for high real-time scenarios, are there any lighter or more suitable alternatives for real-time interaction in the community?
Looking forward to your reply. Thank you