Repository navigation
Replies: 2 comments
|
Yes, this is a known issue. Using declarative ui to render charts with large amounts of data can cause large performance issues. Just like when using echarts in the web, it is also recommended to use canvas mode instead of svg mode. I haven't thought of a good solution yet, but we haven't given up on solving this problem. One way to do this is to implement CanvasRenderingContext2D and then draw the chart by using imperative. In this case there is no need to keep a large number of nodes compared to svg. When the chart changes, it can also be optimized to redraw dirty areas instead of full rendering. |
0 replies
|
If you have good ideas, welcome to discuss them together |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello,
react-native-echartsperforms much better than its webview-based alternatives, but still suffers of performance issues on large datasets.Are there any plans to improve this? Do you know whether it's the svg string conversion or the rendering that's causing the performance issues?
All reactions