Script too slow warning messages about stupid-table-plugin HOT 8 CLOSED

I (think) the problem could be because you are sorting it by moving one tr at a time, which means the browser has to draw this tr each time is moved, and maybe maybe, could be that the same TR moves up and down one too many times unnecessarily, this maybe can be avoided if the data is sorted using arrays and then manipulate the dom with the result. (it may help speed up the sorting)

Also this may help ...

http://stackoverflow.com/questions/1340589/javascript-are-loops-really-faster-in-reverse#13136778

from stupid-table-plugin.

Thanks for the bug report. Your second comment is incorrect, though. I'm not sorting by moving the trs around. See here. That returns an array, and the other columns are rearranged according to the sort map (so that they match the array sorted). The dom is only touched in one spot, which is here.

from stupid-table-plugin.

oh I see, I was just suggesting it, do you think it could be that tables are pretty slow ?

or have any idea as to what it could be ?

from stupid-table-plugin.

Drawing that many elements may just be too slow. It's probably why most table plugins paginate.

from stupid-table-plugin.

You could time how long it takes to reach right before the .append() via https://developers.google.com/chrome-developer-tools/docs/console-api#consoletimelabel, and then see how long the append() takes. I bet the actual rendering of the elements is the bottleneck and not the sort.

from stupid-table-plugin.

when you append, it's a lot faster to use $('table').emty() then append one by one... than trying to redraw the table with the new row on a new position...

Could this be a possible approach ?

from stupid-table-plugin.

We aren't appending one by one. We append the entire HTML

from stupid-table-plugin.

#97 aims to provide performance improvements.

from stupid-table-plugin.