Thanks very much for the info. It looks like my bottleneck is number 2. On Fri, Oct 21, 2011 at 11:32 AM, Uemit <[email protected]> wrote:
> No, CellTable will only render the visible part. > Fetching 500 rows from the server should take too long either. > I assume that the slowness is not related to the rendering in the CellTable > but probably due to fetching and parsing of the 500 rows because you don't > see any difference when you render 5 rows or 500. > So it clearly must be something else. > > There are 3 possible bottlenecks: > > > 1. Fetching the data from the backend: if you use JSON and don't > transfer many fields then 500 rows shouldn't be a big issue (you can verfiy > it by using Firebug and checking the payload size) > 2. Parsing the fetched data: Again with JSON it should be fast enough > to parse 500 rows (not sure about XML) > 3. Rendering the data in a CellTable: if there is no performance > difference between 500 rows and 5 rows then the bottleneck must lie in one > of the previous areas. > > > I have no performance problems fetching around 2000 rows and displaying 50 > of them (using SimplePager). > > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-web-toolkit/-/4F6zBx7p3BkJ. > > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
