You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using this with react-table for row virtualization based on this codesanndbox, things are working but scrolling is not smooth like this example.
Yes, I am doing lots of calculation before rendering but everything is within React.memo or react.callback with proper dependency array, and I have also verified that no recalculation is getting called on every scroll only row rendering is happening.
Here is the Warning from browser as well, where you can see that on an average it is taking 350 ms on every small scroll to calculate and re-rendering new rows. I have reduced this number to 250 after putting all recalculation in react.memo and decreasing overscan to 1, but still warning is there and I can feel the performance issue on i7 CPU.
I am using dynamic size rows but even after using fixed-size rows there is a warning from browser with average delay is up to 175ms on every scroll
So is it recommended to use this library with react-table? if yes is there any good practices needs to follow?
This discussion was converted from issue #70 on October 07, 2020 01:02.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am using this with react-table for row virtualization based on this codesanndbox, things are working but scrolling is not smooth like this example.
Yes, I am doing lots of calculation before rendering but everything is within React.memo or react.callback with proper dependency array, and I have also verified that no recalculation is getting called on every scroll only row rendering is happening.
Here is the Warning from browser as well, where you can see that on an average it is taking 350 ms on every small scroll to calculate and re-rendering new rows. I have reduced this number to 250 after putting all recalculation in react.memo and decreasing overscan to 1, but still warning is there and I can feel the performance issue on i7 CPU.
I am using dynamic size rows but even after using fixed-size rows there is a warning from browser with average delay is up to 175ms on every scroll
So is it recommended to use this library with react-table? if yes is there any good practices needs to follow?
Beta Was this translation helpful? Give feedback.
All reactions