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

Not Optimal for buckets with many objects #51

Open
notfol opened this issue May 7, 2019 · 0 comments
Open

Not Optimal for buckets with many objects #51

notfol opened this issue May 7, 2019 · 0 comments
Assignees

Comments

@notfol
Copy link

notfol commented May 7, 2019

The UI becomes unresponsive when loading a bucket with many objects (100K+). I believe this is because the app is loading all the objects in the bucket in batches of 1000. You may consider paginating the calls to S3, fetching only DataTables pageLength number of objects at a time. Subsequent batches can be fetch by triggering the page event. I believe fnDrawCallback and fnInfoCallback are also called when the next button is clicked.

https://datatables.net/reference/event/page
http://legacy.datatables.net/usage/callbacks#fnDrawCallback
http://legacy.datatables.net/usage/callbacks#fnInfoCallback

@notfol notfol changed the title Not Optimal buckets with many objects Not Optimal for buckets with many objects May 7, 2019
@john-aws john-aws self-assigned this May 8, 2019
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