RPC serialization/deserialization is very slow

329 views
Skip to first unread message

Jacob Glusted Madsen

unread,
Apr 25, 2012, 6:17:19 AM4/25/12
to google-we...@googlegroups.com
Hi, 
We are having problems with serialization/deserialization of RPC data.
This process seems to become very slow when the amount of data increases 
The problem seems to be greatest in ie8
It runs faster in Crome!

Does anyone have any sugestions on how to make the RPC serialization/deserialization run faster ?? 


Paul Robinson

unread,
Apr 25, 2012, 6:44:13 AM4/25/12
to google-we...@googlegroups.com
On 25/04/12 11:17, Jacob Glusted Madsen wrote:
> Does anyone have any sugestions on how to make the RPC serialization/deserialization run faster ??
>
The biggest difference you can make to RPC speed is to send less data over the network. You should make sure you're only sending stuff that you really need to send. This may involve using DTOs to ensure you have the bare minimum your client actually needs.

HTH
Paul

Jens

unread,
Apr 25, 2012, 6:50:42 AM4/25/12
to google-we...@googlegroups.com
Fastest possible solution is to switch to pure JSON string + Overlay Types which would result in nearly no GWT overhead.

If you don't want to switch your RPC mechanism or its still too slow then you have to fetch your data in smaller chunks. For example presenting 10000 objects in a UI list does not make that much sense. Loading chunks of 500 objects while the user scrolls through the list would make more sense. Its like here in Google Groups. Loading all topics at once wouldn't work, thus they load chunks of topics while you scroll through them. 

If you really need that 10000 objects from the beginning you could maybe use a RepeatingCommand and load chunks of 500 objects until you have loaded everything. That way the browser wouldn't lock up, but it will take longer to download and present the data.

-- J.

Jacob Glusted Madsen

unread,
May 7, 2012, 6:39:32 AM5/7/12
to google-we...@googlegroups.com
Thanks for your answer!

We have now tried different solutions to the problem.
We did some experiments using JSON. But it was still to slow.

We ended up with a solution, where we did some redesign of the GUI-interface forcing the user to filter data before loading it.

It seemed to be the only real solution to problem to load less data.
Deserializing large amounts of data just seems to be slow in GWT, especially when running in old browsers like IE8

/jacob

Brandon Donnelson

unread,
May 8, 2012, 4:22:31 PM5/8/12
to google-we...@googlegroups.com
What exactly are you serializing? How big is the object your trying to pass?

Brandon Donnelson
Reply all
Reply to author
Forward
0 new messages