Re: Severe performance problem after upgrading to GWT 1.5.2 (final)
Hello everyone, I tried reproducing the problem and observing differences in speed between FF2 and FF3 on Windows for repeated RPC calls transferring a String from client to server using GWT 1.5.3 and did not observe any significant slowdowns in FF3. I'll also try this out on a Mac to see if I observe any differences there, but before I do, is there any reproducible code that some of you may have that might help reproduce the slowdown on our end? Cheers, -Sumit Chandel On Wed, Oct 22, 2008 at 2:29 AM, Twentyseven <[EMAIL PROTECTED]> wrote: > > Hi, > > We have the same problem on FF3 on Windows ; it seems that with the > 1.5.2 the RPC calls are very slow on FF3. > On Chrome, the application run normally. > > Eric > > On 7 oct, 16:59, Manuel <[EMAIL PROTECTED]> wrote: > > Actually yes. This seems to be slow down in FF3 on my mac. I have > > asked people to test using ff3 on Windows and they say its slower but > > not as sever as on the mac. > > > > Thanks, > > Manuel > > > > On Oct 6, 5:51 am, "Sumit Chandel" <[EMAIL PROTECTED]> wrote: > > > > > Hi Manuel, > > > Thanks for the follow-up. As far as I can tell, there isn't anything > > > introduced between 1.5 RC2 and 1.5.2 that would cause slowdowns on RPC > calls > > > in FF. > > > > > I noticed you mentioned this is especially prevalent in Firefox 3. Do > the > > > RPC calls also slowdown in Firefox 2? It would be good to know if this > is a > > > problem related to changes in FF rather than in GWT. > > > > > Cheers, > > > -Sumit Chandel > > > > > On Fri, Oct 3, 2008 at 4:09 PM, Manuel <[EMAIL PROTECTED]> wrote: > > > > > > We noticed a slow down by just switching from 1.5RC2 to 1.5.2 more > > > > specifically on FireFox 3. I recently tested on Chrome and Safari 3 > > > > and the performance there is significantly better it seems to be well > > > > over 10x faster. I think there might be a bug using the scripting > > > > engine on FireFox and also IE. Or it could be the java scripting > > > > engine on Safari is really that much better. > > > > > > The overall app is much faster on Safari, but i would say the biggest > > > > issue is with RPC calls. > > > > > > On Oct 3, 7:22 am, "Sumit Chandel" <[EMAIL PROTECTED]> wrote: > > > > > Hi Manuel, > > > > > It seems hbatista's slowdown in performance was related to a > database > > > > > change. > > > > > > > In your case, are you still experiencing slowdowns on your RPC > calls? > > > > Also, > > > > > did these slowdowns occur when you went from 1.4.x to 1.5.2, or > were you > > > > > always facing slow RPC calls in your GWT application? > > > > > > > Thanks, > > > > > -Sumit Chandel > > > > > > > On Tue, Sep 30, 2008 at 8:26 PM, Manuel <[EMAIL PROTECTED]> wrote: > > > > > > > > Has anyone figgured this out. I am having sever performance > problems > > > > > > with this. accross the board all 1.5.2 compiled apps are a lot > slower > > > > > > > > On Sep 18, 4:59 am, hbatista <[EMAIL PROTECTED]> wrote: > > > > > > > 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 to1.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, 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 > > > > veryslow > > > > > > > > > in all browsers (bad!). > > > > > > > > > > > Can someone help me debug this problem?- Hide
Re: Severe performance problem after upgrading to GWT 1.5.2 (final)
Hi, We have the same problem on FF3 on Windows ; it seems that with the 1.5.2 the RPC calls are very slow on FF3. On Chrome, the application run normally. Eric On 7 oct, 16:59, Manuel <[EMAIL PROTECTED]> wrote: > Actually yes. This seems to be slow down in FF3 on my mac. I have > asked people to test using ff3 on Windows and they say its slower but > not as sever as on the mac. > > Thanks, > Manuel > > On Oct 6, 5:51 am, "Sumit Chandel" <[EMAIL PROTECTED]> wrote: > > > Hi Manuel, > > Thanks for the follow-up. As far as I can tell, there isn't anything > > introduced between 1.5 RC2 and 1.5.2 that would cause slowdowns on RPC calls > > in FF. > > > I noticed you mentioned this is especially prevalent in Firefox 3. Do the > > RPC calls also slowdown in Firefox 2? It would be good to know if this is a > > problem related to changes in FF rather than in GWT. > > > Cheers, > > -Sumit Chandel > > > On Fri, Oct 3, 2008 at 4:09 PM, Manuel <[EMAIL PROTECTED]> wrote: > > > > We noticed a slow down by just switching from 1.5RC2 to 1.5.2 more > > > specifically on FireFox 3. I recently tested on Chrome and Safari 3 > > > and the performance there is significantly better it seems to be well > > > over 10x faster. I think there might be a bug using the scripting > > > engine on FireFox and also IE. Or it could be the java scripting > > > engine on Safari is really that much better. > > > > The overall app is much faster on Safari, but i would say the biggest > > > issue is with RPC calls. > > > > On Oct 3, 7:22 am, "Sumit Chandel" <[EMAIL PROTECTED]> wrote: > > > > Hi Manuel, > > > > It seems hbatista's slowdown in performance was related to a database > > > > change. > > > > > In your case, are you still experiencing slowdowns on your RPC calls? > > > Also, > > > > did these slowdowns occur when you went from 1.4.x to 1.5.2, or were you > > > > always facing slow RPC calls in your GWT application? > > > > > Thanks, > > > > -Sumit Chandel > > > > > On Tue, Sep 30, 2008 at 8:26 PM, Manuel <[EMAIL PROTECTED]> wrote: > > > > > > Has anyone figgured this out. I am having sever performance problems > > > > > with this. accross the board all 1.5.2 compiled apps are a lot slower > > > > > > On Sep 18, 4:59 am, hbatista <[EMAIL PROTECTED]> wrote: > > > > > > 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 to1.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, 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 > > > veryslow > > > > > > > > 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 Google-Web-Toolkit@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: Severe performance problem after upgrading to GWT 1.5.2 (final)
Actually yes. This seems to be slow down in FF3 on my mac. I have asked people to test using ff3 on Windows and they say its slower but not as sever as on the mac. Thanks, Manuel On Oct 6, 5:51 am, "Sumit Chandel" <[EMAIL PROTECTED]> wrote: > Hi Manuel, > Thanks for the follow-up. As far as I can tell, there isn't anything > introduced between 1.5 RC2 and 1.5.2 that would cause slowdowns on RPC calls > in FF. > > I noticed you mentioned this is especially prevalent in Firefox 3. Do the > RPC calls also slowdown in Firefox 2? It would be good to know if this is a > problem related to changes in FF rather than in GWT. > > Cheers, > -Sumit Chandel > > On Fri, Oct 3, 2008 at 4:09 PM, Manuel <[EMAIL PROTECTED]> wrote: > > > We noticed a slow down by just switching from 1.5RC2 to 1.5.2 more > > specifically on FireFox 3. I recently tested on Chrome and Safari 3 > > and the performance there is significantly better it seems to be well > > over 10x faster. I think there might be a bug using the scripting > > engine on FireFox and also IE. Or it could be the java scripting > > engine on Safari is really that much better. > > > The overall app is much faster on Safari, but i would say the biggest > > issue is with RPC calls. > > > On Oct 3, 7:22 am, "Sumit Chandel" <[EMAIL PROTECTED]> wrote: > > > Hi Manuel, > > > It seems hbatista's slowdown in performance was related to a database > > > change. > > > > In your case, are you still experiencing slowdowns on your RPC calls? > > Also, > > > did these slowdowns occur when you went from 1.4.x to 1.5.2, or were you > > > always facing slow RPC calls in your GWT application? > > > > Thanks, > > > -Sumit Chandel > > > > On Tue, Sep 30, 2008 at 8:26 PM, Manuel <[EMAIL PROTECTED]> wrote: > > > > > Has anyone figgured this out. I am having sever performance problems > > > > with this. accross the board all 1.5.2 compiled apps are a lot slower > > > > > On Sep 18, 4:59 am, hbatista <[EMAIL PROTECTED]> wrote: > > > > > 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 to1.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, 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 > > veryslow > > > > > > > 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 Google-Web-Toolkit@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: Severe performance problem after upgrading to GWT 1.5.2 (final)
Hi Manuel, Thanks for the follow-up. As far as I can tell, there isn't anything introduced between 1.5 RC2 and 1.5.2 that would cause slowdowns on RPC calls in FF. I noticed you mentioned this is especially prevalent in Firefox 3. Do the RPC calls also slowdown in Firefox 2? It would be good to know if this is a problem related to changes in FF rather than in GWT. Cheers, -Sumit Chandel On Fri, Oct 3, 2008 at 4:09 PM, Manuel <[EMAIL PROTECTED]> wrote: > > We noticed a slow down by just switching from 1.5RC2 to 1.5.2 more > specifically on FireFox 3. I recently tested on Chrome and Safari 3 > and the performance there is significantly better it seems to be well > over 10x faster. I think there might be a bug using the scripting > engine on FireFox and also IE. Or it could be the java scripting > engine on Safari is really that much better. > > The overall app is much faster on Safari, but i would say the biggest > issue is with RPC calls. > > > On Oct 3, 7:22 am, "Sumit Chandel" <[EMAIL PROTECTED]> wrote: > > Hi Manuel, > > It seems hbatista's slowdown in performance was related to a database > > change. > > > > In your case, are you still experiencing slowdowns on your RPC calls? > Also, > > did these slowdowns occur when you went from 1.4.x to 1.5.2, or were you > > always facing slow RPC calls in your GWT application? > > > > Thanks, > > -Sumit Chandel > > > > On Tue, Sep 30, 2008 at 8:26 PM, Manuel <[EMAIL PROTECTED]> wrote: > > > > > Has anyone figgured this out. I am having sever performance problems > > > with this. accross the board all 1.5.2 compiled apps are a lot slower > > > > > On Sep 18, 4:59 am, hbatista <[EMAIL PROTECTED]> wrote: > > > > 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 to1.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, 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 > veryslow > > > > > > 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 Google-Web-Toolkit@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: Severe performance problem after upgrading to GWT 1.5.2 (final)
We noticed a slow down by just switching from 1.5RC2 to 1.5.2 more specifically on FireFox 3. I recently tested on Chrome and Safari 3 and the performance there is significantly better it seems to be well over 10x faster. I think there might be a bug using the scripting engine on FireFox and also IE. Or it could be the java scripting engine on Safari is really that much better. The overall app is much faster on Safari, but i would say the biggest issue is with RPC calls. On Oct 3, 7:22 am, "Sumit Chandel" <[EMAIL PROTECTED]> wrote: > Hi Manuel, > It seems hbatista's slowdown in performance was related to a database > change. > > In your case, are you still experiencing slowdowns on your RPC calls? Also, > did these slowdowns occur when you went from 1.4.x to 1.5.2, or were you > always facing slow RPC calls in your GWT application? > > Thanks, > -Sumit Chandel > > On Tue, Sep 30, 2008 at 8:26 PM, Manuel <[EMAIL PROTECTED]> wrote: > > > Has anyone figgured this out. I am having sever performance problems > > with this. accross the board all 1.5.2 compiled apps are a lot slower > > > On Sep 18, 4:59 am, hbatista <[EMAIL PROTECTED]> wrote: > > > 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 to1.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, 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 veryslow > > > > > 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 Google-Web-Toolkit@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: Severe performance problem after upgrading to GWT 1.5.2 (final)
Hi Manuel, It seems hbatista's slowdown in performance was related to a database change. In your case, are you still experiencing slowdowns on your RPC calls? Also, did these slowdowns occur when you went from 1.4.x to 1.5.2, or were you always facing slow RPC calls in your GWT application? Thanks, -Sumit Chandel On Tue, Sep 30, 2008 at 8:26 PM, Manuel <[EMAIL PROTECTED]> wrote: > > Has anyone figgured this out. I am having sever performance problems > with this. accross the board all 1.5.2 compiled apps are a lot slower > > > On Sep 18, 4:59 am, hbatista <[EMAIL PROTECTED]> wrote: > > 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 to1.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, 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 veryslow > > > > 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 Google-Web-Toolkit@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: Severe performance problem after upgrading to GWT 1.5.2 (final)
In my case I made some mistake while profiling my code... turns ot that for some reason the database access got really slow. I switched the database drivers (from jtds to the microsoft jdbc driver for sql server) and everything went back to normal. On Sep 30, 8:20 pm, Manuel <[EMAIL PROTECTED]> wrote: > Has anyone figured what is going.. I am experiencing same problems.. > everything seems slower. > > On Sep 18, 4:59 am, hbatista <[EMAIL PROTECTED]> wrote: > > > > > 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 to1.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, 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 veryslow > > > > in all browsers (bad!). > > > > > Can someone help me debug this problem?- Hide quoted text - > > > > - Show quoted text -- 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 Google-Web-Toolkit@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: Severe performance problem after upgrading to GWT 1.5.2 (final)
Has anyone figgured this out. I am having sever performance problems with this. accross the board all 1.5.2 compiled apps are a lot slower On Sep 18, 4:59 am, hbatista <[EMAIL PROTECTED]> wrote: > 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 to1.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, 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 veryslow > > > 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 Google-Web-Toolkit@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: Severe performance problem after upgrading to GWT 1.5.2 (final)
Has anyone figured what is going.. I am experiencing same problems.. everything seems slower. On Sep 18, 4:59 am, hbatista <[EMAIL PROTECTED]> wrote: > 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 to1.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, 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 veryslow > > > 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 Google-Web-Toolkit@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: Severe performance problem after upgrading to GWT 1.5.2 (final)
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, 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 Google-Web-Toolkit@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: Severe performance problem after upgrading to GWT 1.5.2 (final)
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, 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? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
