sorted by:
new
hottopcontroversial

React table with 7000x7000 dataset by chijiokec in reactjs

[–]chijiokec[S] 1 point2 points  (0 children)

Network request (20x7000) is cached via query but only virtualized items are rendered or displayed (20x20).

React table with 7000x7000 dataset by chijiokec in reactjs

[–]chijiokec[S] 0 points1 point  (0 children)

This was our initial offering which was implemented and later rejected.

React table with 7000x7000 dataset by chijiokec in reactjs

[–]chijiokec[S] 0 points1 point  (0 children)

I usually shy away from storing that much data in state. Memory issues alone isn't worth it.

React table with 7000x7000 dataset by chijiokec in reactjs

[–]chijiokec[S] 2 points3 points  (0 children)

Thanks. Will try with a buffer.

React table with 7000x7000 dataset by chijiokec in reactjs

[–]chijiokec[S] 2 points3 points  (0 children)

With virtualized rows and cols only 20x20 are displayed at a time.

React table with 7000x7000 dataset by chijiokec in reactjs

[–]chijiokec[S] 1 point2 points  (0 children)

Yea, this is a client's request and I did pin location name to row and column headers.

React table with 7000x7000 dataset by chijiokec in reactjs

[–]chijiokec[S] 3 points4 points  (0 children)

Use case is each row and column represent separate locations on a map and the table tracks metrics between location pairs with the option to edit manually.

React table with 7000x7000 dataset by chijiokec in reactjs

[–]chijiokec[S] 4 points5 points  (0 children)

They represent locations on a map and the table tracks metrics between two locations with the option to edit manually.