Re: Cell Table Data Handling & Performance

On Mon, Jul 25, 2011 at 6:49 AM, BST <babusri.21@gmail.com> wrote:

Hi,

I have successfully managed to use a Cell table & an abstract pager to
fetch the new set of data from an RPC and display them on the cell
table. Many thanks to the developer discussions and Developer Guide.

But I do have a few concerns, as I plan to use it for large data sets,
maybe like 10k objects. The Developer Guide does mention Cell table
can handle large data sets, but I wanna know how large is large, any
approximate number of objects in a list? Also a few other questions
below,

The maximum page size is heavily dependent on the app and the data being displayed, but some teams have gotten into the 250-500 rows per page.  Assuming your backend can provide the data quickly, the limiting performance factor of CellTable is rendering, and rendering a 500 row table isn't instantaneous.

Will my browser performance become sluggish if I load too many objects
simultaneously ? For E.g lets say I store a list of Contact objects,
with a pic of the contact and other textual information such as name,
address and mail. The image might be a blob or a Base64 string.

All modern browsers should be able to handle an array of a few thousand Contact objects without a problem, but if you are searching through the array, that might be slow.  You also have to consider bandwidth constraints.  Can you load the Contacts on demand and push the processing to the server?

Is there a performance lag while using the pager on a really large
data set?

There is no performance lag in CellTable itself.  If your backend can provide data within a range, paging is a better experience than loading 10,000 objects upfront.

If you are not sure, maybe you can tell me this, how the object
handling in a list w.r.t Cell Table is done , and do the objects exist
once objects are converted to html in the Cell Table on the client
Side?

CellTable caches the row values within the current page so it can pass the row values to Cells, and so it can re-render rows when needed.  When you switch pages, the row values of the previous page are dumped.

Regards,
BST


--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
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 google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.