Tim Fennell wrote: > Returning a 30K table as an HTML table in one single request will > actually have pretty poor rendering time in the browser.
I agree, but if it's required by users... > We have > some pages at work that show 3-5K rows regularly (yes, it is useful > sometimes), I've tried to raise the page size I use up to 30k rows (instead of 30) for a table containing 15 columns. With IE6 the table was rendered and fully displayed after around 40s (gzipped over ssl) IE6 now uses 290Mo of RAM and used 100% of my cpu during that time. Same table with Firefox 3: 2min30, same amount of memory used. In both case, the table wasn't rendered until the end. I use hibernate -> stripes -> displaytag. > I think if you want a snappy solution you'll have to do what others > have recommended: send the first X rows down and then use AJAX to > dynamically load the rest either on-demand, or simply sequentially > after the page loads. Probably using JSON would lead to more compact > representation and faster parsing the JS layer as opposed to XML, but > I'm not sure how big a different that would make. I 'd also try to send CSV content with Excel content type, perharps will it be faster (and easier to sort after table display) ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Stripes-users mailing list Stripes-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/stripes-users
