javascript table sorting/paging (client-side). How big is too big?

Posted by Aheho on Stack Overflow See other posts from Stack Overflow or by Aheho
Published on 2010-06-18T01:23:30Z Indexed on 2010/06/18 1:33 UTC
Read the original article Hit count: 345

Filed under:
|
|

I'm using a jQuery plugin called Tablesorter to do client-side sorting of a log table in one of my applications. I am also making use of the tablepager add-in.

I really like the responsiveness that client-side sorting and paging brings to the party. I also like how you don't have to hit the web server or database repeatedly.

However I can see that, in time, the log I'm displaying could grow quite large. I'm sure there comes a point where client-side paging and sorting is going to be impractical. What point will this technique begin to collapse under it's own weight? 500 records? 2000 records? 10,000 records?

EDIT: In nutshell, what criteria would you use to determine if you are going to use client-side sorting/paging as opposed to server-side paging? Does the size of expected result set factor into your decision? Where is the tipping point?

© Stack Overflow or respective owner

Related posts about JavaScript

Related posts about jQuery