-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Paginator performance/crash issue #6905
Comments
tw15egan
added
type: duplicate 👯
and removed
status: needs triage 🕵️♀️
type: bug 🐛
labels
Nov 4, 2020
Closing as duplicate |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The paginator is not designed to be used with many pages. We have results that have up to 100k results,
and the best the paginator does is to create a really long delay in page rendering.
If we tried 500k results, the paginator crashed on stack. Do you have a recursion there?
This needs to work in miliseconds, not delay page renders and not crash.
try this on any page and measure response time.
<Pagination
page={1}
pageSize={20}
itemsPerPageText="Items per page:"
pageSizes={[10, 20, 30, 40, 50]}
onChange={(e) => {
console.log('pagination changed');
}}
totalItems={123456}
/>
The text was updated successfully, but these errors were encountered: