Hi Daniel, We log the time stamp just after the RPC is fired from client. And, log another time stamp the moment RPC reaches server. We calculate the time that RPC takes to reach servlet from the client by taking the difference between these 2 timings. At present, the client and the server both are on the same machine.
Can you plz explain the rest 2 points that you have asked? I'm not clear about these 2 points. On Aug 21, 11:43 am, Daniel Jue <[email protected]> wrote: > Is there a way to keep an eye on the number of handlers are are in > existence? At what point in the dispatch are you starting the timer? > Are you using an event bus? > > On Fri, Aug 21, 2009 at 2:32 AM, Vikrant<[email protected]> wrote: > > > Hi, > > > Forgot to mention that the below mentioned issue is occurring only in > > Internet Explorer 6. We did not face any such performance degradation > > issue in Internet Explorer 7. > > > But, we are bound to use IE 6. So, something has to be done to resolve > > the issue. > > > Any help would be highly appreciated. > > > Regards, > > > Vikrant > > > On Aug 19, 4:33 pm, Vikrant Chourasia <[email protected]> wrote: > >> Hi, > > >> We have a screen that contains around 350 controls. We are facing a > >> heavy > >> performance degradation issue when we repetitively open this screen > >> and > >> close the same. When analyzed, what we found taking, comparatively, > >> longer > >> each time, is the RPC time (to be more precise what is getting majorly > >> increased each time is the time difference between the timings when > >> RPC > >> gets dispatched from Client and reaches Server). > > >> Following are some stats on the same: > > >> 1st RPC call: > > >> Client to Server = 3.196 seconds > >> Server operations = 1.879 seconds > >> Server to Client = 0.063 seconds > > >> 10th RPC call: > > >> Client to Server = 5.451 seconds > >> Server operations = 2.569 seconds > >> Server to Client = 0.094 seconds > > >> Which clearly shows that after 10 RPC calls performance gets degraded > >> by > >> around 3 seconds. > > >> There are other operations too that adds to performance degradation > >> after > >> continuous iterations, but the one that heavily contributes to the > >> performance degradation is the RPC one mentioned above. > > >> We are using Internet Explorer 6. What we do on close of this screen > >> is > >> clearing the absolute panel and assigning null to the reference of the > >> screen i.e. > > >> baseCurrent.getAbsMainPanel().clear(); > >> baseCurrent = null; > > >> where baseCurrent is the reference of current screen. > > >> Any help would be highly appreciated. > > >> Regards, > > >> Vikrant --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
