Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

performance issue with 500+ elements #70

Open
danvln opened this issue Oct 15, 2020 · 2 comments
Open

performance issue with 500+ elements #70

danvln opened this issue Oct 15, 2020 · 2 comments

Comments

@danvln
Copy link

danvln commented Oct 15, 2020

Hi @kutlugsahin,

I see that the this is super slow when it starts to grow. At 500 elements is already unusable. Is this expected?

Thanks!

@trungquandev
Copy link

trungquandev commented Jun 19, 2021

@danvln
I guess that your problem is caused by re-rendering unnecessary components, you can check with chrome extension: React developer tools.

If I'm right, you can use shouldComponentUpdate (for Class Component) or React.memo, useCallBack, useMemo (for Functional Components - React Hooks) to avoid re-render unnecessary columns or cards.

@rwaidaAlmehanni
Copy link

i got the same issue, when i try to use render and send the ref to react-virtuoso => it return error because the list will render after the ref.current is not null

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants