[Question] useNodeRender performance or what

[fabrifls]

🙋 SDK Version

0.5.1

📌 Layout

Fixed layout?

📝 Question Description

I have trees with more than 300 nodes, and what I'm noticing is that having them open for a short time starts to drain the layout's performance (laggin).

What I see in the logs is the warning:

Listeners length >= 175 Error Component Stack

It's hard to debug, but when I comment out the line const nodeRender = useNodeRender() in the BaseNode, the warning doesn't appear, so it seems to be coming from there.

Do you think flows can have a node limit within which performance is maintained?

Any recommendations for trees with a large number of nodes?

[louisyoungx]

In useNodeRender, each node triggers some event listeners. When there are many nodes, emitter warnings are normal, and I'm considering hiding this warning.

Here's a performance test chart from the simplest example for reference. If your node render DOM is complex, performance will be further reduced.

[fabrifls]

Okay, maybe not triggering the warnings would help reduce latency a bit too.

What did you use for the measurement? So I can replicate it in my environment.

[louisyoungx]

I use the chrome official library https://github.com/GoogleChrome/web-vitals to measure performance.

[sanmaopep]

@louisyoungx we can also modify 175 to higher digits, to prevent memory leaks problems

[fabrifls]

@louisyoungx we can also modify 175 to higher digits, to prevent memory leaks problems

Perhaps some strict could be set in FixedLayoutProps to avoid the memory leak caused by the console:

...,
warning: {
    strict: boolean
}