I am having the same type of problem - fetching and displaying huge amount
of data via RPC (displayed in a celltable) runs extremly slow.
Our analysis indicates, that it is the serialization/deserialization that
causes the problem.
The rendering of the celltable is actually extremly fast, at
Any sugestions on how to make the serialization/deserialization run
faster ??
Use pure JSON with overlay types (almost no overhead) and if its still too
slow for you then you have to fetch your data in smaller chunks.
-- J.
--
You received this message because you are subscribed to the
Wow ! how many rows!!! In IE is very slow. Very rarely requirement, is
better to generate an excel file. I think with GWT at now is impossible to
do fast. I think you must generate a html file in server side and then
displayed.
Juan
2011/6/7 Leela rcleel...@gmail.com
Hi,
I'm using GWT 2.2.
8000 rows is too many to display at once. Even a HTML file probably take a
while to load, and the scrollbars become almost unusable because you don't
have the fidelity to narrow in on a row. The slow script warning happens
when you block the UI for too long (sometimes measured in seconds, other
8000 rows ???
If that s the requirement then maybe you should revisit the requirement
instead of trying to implement something like displaying 8000 rows at once.
Who is able to process 8000 rows of data at once?
2011/6/7 John LaBanca jlaba...@google.com
8000 rows is too many to display at
Thanks for the suggestions.
8000 is the max limit for the data in our case. Though this is not a
practical scenario, we just thought of handling the worst case. We
wanted to identify if the problem was in our coding or if Celltable
has some issue with such large data.
As John suggested I would
are you sure that the bottleneck is the display of the data??
if you are making rpc calls to get the 8000 data to display the critical
poit could be the rpc deserialization. try to create random data on the
client to check this.
--
You received this message because you are subscribed to the
