> > - the rpc is quite slow. i am using it to return a few thousand by > eleven column of data(String)....
a) RPC is *much* slower in hosted mode than deployed in web mode. You should time your RPC performance (separately to the table "draw" time) when deployed to find out how it is really performing b) having said that, fetching several thousand rows of data and displaying it in one operation is likely to be unacceptably slow. It takes javascript engines quite a long time attach thousands of HTML elements to the DOM. It is generally much faster to do it in page- fulls even though it takes multiple RPC calls to do it that way. You might want to check out the PagingScrollTable in the incubator. > - i have a tabset within my application which i copied from the > smartgwt showcase.... when i click on new tab with google map on > it...... it will normally hang and need a few minutes to finally > display the result. sometimes, it will hang forever. > SmartGWT is a GWT wrapper around a javascript library. It might be difficult to figure out why it is not performing well for your use case, and very difficult to do anything about it if you can. Generally speaking, if you use pure GWT you will get higher performance and more flexibility and code transparency. > can you give me some links to these tutorials? if you have any..... > > thanks again.. > > On Apr 15, 3:13 pm, Thomas Broyer <t.bro...@gmail.com> wrote: > > > On 15 avr, 13:51, ytbryan <ytbr...@gmail.com> wrote: > > > > hi folks, > > > > my application has been running very slowly and i would like to know > > > why. > > > You could try compiling in -style DETAILED (or at least PRETTY) and > > run a JavaScript profiler (Firebug or IE8 developer tools). > > GWT comes with a benchmark framework, but you'd have to know what you > > want/have to measure... > > > > can somebody advise me on what are the common bottleneck that i need > > > to optimise? I am pretty new with gwt. > > > 1. optimize network exchanges (generally, you'd better have 1 RPC call > > return 3 "kinds" of data, than 3 RPC calls) > > 2. but GWT-RPC might be slow, particularly while serializing/ > > deserializing large object graphs > > 3. when updating the UI, working with hidden (display:none) or, even > > better, detached widgets is faster; sometimes, building a new widget > > "from scratch", populating it and replacing an existing equivalent > > widget might be faster than updating the existing widget > > 4. rendering-wise, try to set table-layout:fixed on your tables > > (including Horizontal/VerticalPanel, FlexTable, Grid, DecoratorPanel, > > DecoratedPopupPanel, DialogBox, etc.) > > > 5. what does "slow" mean? --~--~---------~--~----~------------~-------~--~----~ 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 google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
