Bryan, As MorningZ pointed out, it's usually not the actual sorting that's slow--it's the redrawing. DOM manipulations of <table /> elements is notoriously slow.
-Dan On Thu, Apr 9, 2009 at 3:36 PM, MorningZ <morni...@gmail.com> wrote: > > I'd look at doing some server side sorting if you are looking for > speed... it's a lot of work for the plugin to sort the client side > data and then redraw 400 rows of data > > > > On Apr 9, 3:09 pm, csi95 <bmomal...@gmail.com> wrote: > > Hi folks, > > > > I've just started using tablesorter for one of my projects, and overall I > > love it. Does just what I need. > > > > The one issue I've come across is that it's S-L-O-W! On a small table, > it's > > just fine. Once I get up to about 400 rows, however, it takes a long > time. > > 6 seconds before the list appears sorted, and another 10 seconds before I > > actually regain control of the browser (Firefox 3.08 / Win32 in this > case). > > > > Is this normal? Should it really take that long to sort 400 rows of > data? > > > > I could understand if it were 4,000 rows, but 400 doesn't seem like much. > > In fact it would probably be quicker to just do a round-trip to the > server > > and let the database do the sorting. > > > > I'm looking for some practical experience and / or suggestions from > anyone > > who may be working with tablesorter on large tables. > > > > Thanks! > > > > - Bryan > > -- > > View this message in context: > http://www.nabble.com/tablesorter-Speed-issues-tp22977435s27240p22977... > > Sent from the jQuery General Discussion mailing list archive at > Nabble.com. >
