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

Pagination with many rows per page (e.g. 100 records) is too slow in 'table' editing mode #1321

Open
1 task done
BigSamu opened this issue Dec 4, 2024 · 2 comments
Open
1 task done

Comments

@BigSamu
Copy link

BigSamu commented Dec 4, 2024

material-react-table version

3.0.1

react & react-dom versions

18.3.1

Describe the bug and the steps to reproduce it

Following same bug in issue Virtualized rows are too slow in 'table' editing mode (Issue 847), when changing number of rows per page from a small amount to large amount (e.g. 5 rows per page to 100 per page) using 'table' editing mode, the load is significally slow.

Minimal, Reproducible Example - (Optional, but Recommended)

https://codesandbox.io/p/devbox/table-inputs-with-100-rows-rf2h3x

Screenshots or Videos (Optional)

Recording.2024-12-04.171501.mp4

Do you intend to try to help solve this bug with your own PR?

None

Terms

  • I understand that if my bug cannot be reliably reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.
@KevinVandy
Copy link
Owner

You can change the number of rows that are shown in the dropdown. Maybe just cap at 50

@BigSamu
Copy link
Author

BigSamu commented Dec 9, 2024

You can change the number of rows that are shown in the dropdown. Maybe just cap at 50

Hi @KevinVandy, thanks for your reply. Yeah I did that and performance improved. But I wonder if this could be fixed or not in MRT. If not, is there a way to put a spinning wheel or skeleton bars, thus you can show a user that data is being loaded?

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

2 participants