Skip to content

Severe performance issues with larger data sets #209

@danielcrk

Description

@danielcrk

I'm not really sure what constitutes a "large" data set in this case. I have a LineChart with around 1200 points and it grossly affects performance of the entire screen, including scrolling. While trying to debug this, I've reduced the chart to the bare essentials (no interactions, lines, legends etc, just a single LineChart.Path) and the issue clearly stems from the Path itself.

Is 1200 points simply too much? It seems like the performance noticeably starts degrading already after 200-300 or so.

(I'm working in a huge project and still haven't completely ruled out external issues. It's hard to test but I also have a feeling that a big performance degradation happened after migrating the project to React Native 0.78 and the new architecture. I could swear wagmi was much faster before, but have no backup for that claim yet. My feeling is that the React Native upgrade introduced performance issues with reanimated itself.)

TL;DR: What would you consider a reasonable amount of data points? What is a reasonable expectation?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions