It's really going to depend on the amount of data you're trying to display at once. You need to be a bit more specific as to what you are doing, but the general rules of thumb are:
- lazy load UI elements, don't load everything at once - if you need to display a lot of data, paginate it so you don't have to pull a lot of information from the server. - if have to load of widgets/display a lot of data, take a look at IncrementalCommand to let the brower breath so the UI doesn't hang: http://google-web-toolkit.googlecode.com/svn/javadoc/1.6/com/google/gwt/user/client/IncrementalCommand.html - don't create a lot of widgets if you don't have to, think about using the DOM classes. Hope that helps, -- Arthur Kalmenson On Thu, Jun 25, 2009 at 1:18 AM, Ananth <[email protected]> wrote: > > Hi All, > > We are using GWT 1.4.61. Currently we are facing performance issues to > load a screen it takes minimum 5-8 secs. Each screen in our > application takes minimum 5 secs to load. > And we are using web service call for database communication. > Let me know up to what > size we can transfer data from server to client? > In case of performance issue, GWT is taking long time to render > a screen . > > Please advice how to improve performance especially rendering time is > taking more than rpc call. > > Thanks, > Ananth. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
