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

Extremely slow perfomance with large dynamic tables #770

Closed
SergeyKiriyenko opened this issue Nov 22, 2014 · 4 comments
Closed

Extremely slow perfomance with large dynamic tables #770

SergeyKiriyenko opened this issue Nov 22, 2014 · 4 comments

Comments

@SergeyKiriyenko
Copy link

I am currently trying to implement Filter Widget External Search with Tablesorter into dynamic tables. However, with small tables (up to 10K rows) everything works fine. But with large datas (more than 10K rows) everything stucks and the page doesn't respond. Is there any way to somehow optimize the performance and make the filter widget work with more than 10K rows. I'm using TableSorter (FORK) 2.18.3, tablesorter (FORK) pager plugin updated 11/3/2014 (v2.18.2) and tableSorter (FORK) 2.16+ widgets - updated 11/7/2014 (v2.18.3).

@Mottie
Copy link
Owner

Mottie commented Nov 24, 2014

Hi @SergeyKiriyenko!

10K rows? Wow, I'd call a table with 1000+ rows a large table.

Anyway, I think these are unrealistic expectations. As I mention in issue #273, a large table would make it unusable on a mobile device. It would be best to serve up a subset of data from your server.

@Mottie
Copy link
Owner

Mottie commented Dec 23, 2014

I'm guessing this issue has been resolved, so I'm going to close it. If you continue to have problems, please feel free to continue this discussion.

@Mottie Mottie closed this as completed Dec 23, 2014
@sennz
Copy link

sennz commented Jun 23, 2015

Hi
I have a table with 20 col and around 8000 rows, it takes long time to load, filter or sort. How can i improve the performance. Also How can I show a progress bar or a overlay so that user get noticed that the table is not ready.
Thanks in advance.

@Francks11
Copy link

Hello @sennz,

tablesorter is not optimize for huge table data for now...

The solution is to implement virtual scrollbar and add in DOM only visible table row... Which this technic, we can have table with millions rows...

But this isn't implemented yet...

Mottie said in issue #933, that he is looking about Clusterize.js http://nexts.github.io/Clusterize.js/.

How works Clusterize ?

The main idea is not to pollute DOM with all used tags. Instead of that - it splits the list to clusters, then shows elements for current scroll position and adds extra rows to top and bottom of the list to emulate full height of table so that browser shows scrollbar as for full list

@Mottie, It is for when the implementation of Clusterize? :-p

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants