Derrell Lipman wrote: > > You might also just try it, even with all 28 sorting states, to see just > how > long it takes initially when loading the data. If it completes before the > browser times out on JavaScript execution time, you may be ok. :-) >
ha ha - Well, I am not sure I want to try :) But anyway, at init stage, I load the 80000 by sets of 10000. Derrell Lipman wrote: > > Just how long is it currently taking to sort when you click on a column? > GC: ~3-6 sec FF3.6: ~3-8 sec IE8: ~20sec-crash but it also depends on each column's strings average length Anyway, I just noticed that IE can't even handle more than ~59600 rows (at least in my case). So, switching to the remoteModel is not an eventuality anymore. What I think I'll do is to store the result in the HTML5 storage / Google Gears SQLite Databas when a remote request is done to reduce the number of request - but of course, there are those 5MB storage limit :(. So, when the final user will scroll or sort the datas, I'll first check if the targeted records are already stored locally and then query or not the local database - it may reduce the number of remote calls. Benoît -- View this message in context: http://qooxdoo.678.n2.nabble.com/Array-sort-vs-HTML5-Google-Gears-SQLite-orderby-benchmark-tp5487657p5488589.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
