Configuration: SmartGWT version 2.2 (also tried 2.3 nightly), GWT 1.5.3
My application uses the ListGrid in virtual pagination mode. I have a servlet that is hooked up via the RestDataSource to provide XML using the <startRow>, <endRow> and <totalRows> elements. My data source can provide over 1M rows, 75 at a time.
The brick wall that I've run into involves the ListGrid running under IE (either in the GWT 1.5.3 hosted mode or in IE in production mode). Once I scroll past 10,000 rows, IE basically hangs - sometimes with the dreaded "script running slowly" message and sometimes the list grid just appears to show no rows (even though scroll bar stays in the position I dragged it to).
I did install a ListGrid.addDataArrivedHandler and I see the 75 rows are being returned pretty quickly after the scrollbar "button" dragging stops. So I know it isn't a problem with the server side taking too long to serve the data.
The amount of "virtual" data shouldn't matter as long as the ListGrid is only attempting to work with the max of 75 rows at a time with the much larger total amount - but I'm wondering if it is doing something internally that really slows down after 10,000 rows.
Firefox and Chrome browsers do not exhibit this problem - could be due to their faster javascript engines.
Any suggestions or hints of where to look?
thanks,
Tom
My application uses the ListGrid in virtual pagination mode. I have a servlet that is hooked up via the RestDataSource to provide XML using the <startRow>, <endRow> and <totalRows> elements. My data source can provide over 1M rows, 75 at a time.
The brick wall that I've run into involves the ListGrid running under IE (either in the GWT 1.5.3 hosted mode or in IE in production mode). Once I scroll past 10,000 rows, IE basically hangs - sometimes with the dreaded "script running slowly" message and sometimes the list grid just appears to show no rows (even though scroll bar stays in the position I dragged it to).
I did install a ListGrid.addDataArrivedHandler and I see the 75 rows are being returned pretty quickly after the scrollbar "button" dragging stops. So I know it isn't a problem with the server side taking too long to serve the data.
The amount of "virtual" data shouldn't matter as long as the ListGrid is only attempting to work with the max of 75 rows at a time with the much larger total amount - but I'm wondering if it is doing something internally that really slows down after 10,000 rows.
Firefox and Chrome browsers do not exhibit this problem - could be due to their faster javascript engines.
Any suggestions or hints of where to look?
thanks,
Tom
Comment