Stress test performance
See original GitHub issueHi! I’ve noticed that stress test performance in the examples is quite poor (10x10 is really not a very big graph). I think it could be fixed with these improvements:
- batch
updateNodeDimensionscalls on initial render (this seems to be a bottleneck) - render only nodes in view (given that they already use ResizeObserver, it shouldn’t be too hard)
I’ve already done the same performance patch for https://github.com/MrBlenny/react-flow-chart a while ago (https://github.com/MrBlenny/react-flow-chart/pull/7), if you are interested, I can try to make a similar PR for this project (I hope this one will have a better maintenance in future)
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:33 (15 by maintainers)
Top Results From Across the Web
Performance Testing vs. Load Testing vs. Stress Testing
A stress test is a type of performance test that checks the upper limits of your system by testing it under extreme loads,...
Read more >Load Testing vs Stress Testing vs Performance Testing - Guru99
Stress testing is a type of testing that determines the stability and robustness of the system. It is a non-functional testing technique. This ......
Read more >Performance Testing vs Load Testing vs Stress Testing ...
Stress tests are executed to identify the application behaviour when the application is subjected to a far greater load than it is expected...
Read more >Difference between Performance and Stress Testing
Stress testing is the subset of performance testing. 3. It aims to determine the behavior of an application under normal conditions. It aims...
Read more >Performance Testing, Load Testing & Stress Testing Explained
Stress testing is testing how an application, software, or website performs when under extreme pressure—an unexpected load. We increase the load ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

We wanted to do a next version without or at least with few as possible breaking changes. Since easy-peasy uses redux we only have to make a few adjustments and the api can stay the same. Maybe for v10.0.0 we could think about using recoil or something similar.
The codesandbox seems to be the default codesandbox.
Since react flow is not canvas/webgl based it’s meant to be used for smaller/midsize flows. Everything above a few hundred nodes (depending how complex the nodes are) will be hard to handle I guess.