Thanks for the suggestion, but changing data types didn't help. I did not profile my code, but the observed behavior is: 1. RPC call is made 2. server side method runs and returns (quickly!) 3. ... huge delay with no CPU activity ... 4. finally client side onSuccess() RPC callback runs
What could be happening on step 3 ? I took a quick look at the serializer source code, but it's too different from 1.4.60 to compare side by side. On Sep 18, 2:06 am, Tim <[EMAIL PROTECTED]> wrote: > not sure, but maybe there are some datatype penalty issues (long vs > double etc). Did you profile your server side code? > > On Sep 17, 10:28 am, hbatista <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > I've just upgraded one of my projects from 1.4.60 to 1.5.2, and > > everything went very smoothly, but... > > when my application tries to fetch a large number of objects from the > > server (via RPC, returns HashMap<Integer,xxx>, about 6000 entries) it > > takes a very very long time! > > > Before the upgrade this was very fast (at least in Firefox and Chrome, > > not in IE). > > > Strangely, while waiting for the RPC call to return there is NO cpu > > activity... > > > For me this seems related to some deep changes in the serialization > > code (taking a guess here), before the upgrade trying to fetch so many > > records from the server would crash IE with 'JavaScript SyntaxError > > exception: Out of memory', while now it works (good!) but is very slow > > in all browsers (bad!). > > > Can someone help me debug this problem?- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
