> > Technically, in the very first request, the server already knows user > browsers' type, is that feasible to: > combine 1), 2) and 3) together or > combine 1) and 2) together or > some other consideration >
You are right, this is possible. See this discussion thread - http://groups.google.com/group/google-web-toolkit/browse_thread/thread/5ddf93a126cc9e47/2f41ef3044145b5a?lnk=gst&q=Determining+Permutation+on+Server *But*, before going down that optimization path, there are several other low-hanging-fruits to speed up your website. I looked at your website via firebug, and the following issues come to my mind - 1. *.cache.xxx file don't have a 'far into the future' expires header. 2. Several (30 or so) images get downloaded at startup. None of these images have aggressive cache settings. You are not using GWTs ImageBundles to potentially inline these images. 3. You have atleast 2 RPC calls at startup (getDayContent and getTargettedContent).The response of these calls is known ahead of time (since they don't depend on any user input), and hence you could potentially inline their response in the html and then use a Dictionary to read it in onModuleLoad. Or you could use a ClientBundle to compile the data with your application. Either way, you save two important 'pseudo-asnyc' requests that delay initial rendering of your application. 4. I see you have a custom implementation to trace performance events. Have you taken a look at GWTs Lightweight Metrics<http://code.google.com/webtoolkit/doc/latest/DevGuideLightweightMetrics.html> ? --Sri On 7 May 2010 02:21, Michael W <[email protected]> wrote: > We launched our GWT production of http://www.holidayinn.com few months > ago and we are in the phrase to tune the performance. > > We see quick high percentage of traffics coming from nocach.js and > cache.html, and just thinking how to reduce over all traffics. > > The normal flow of GWT would be like followings: > 1) The user request the website, the first server call is to get > generated html file (from JSP/Servlet) > 2) Then browser sends second request to fetch nocach.js with > <script type="text/javascript" language="javascript" src="/ > directory/xyz.nocache.js"></script> > 3) Based on the user browser's type, the browser send third request to > get .cache.html > 4) Few RPC calls to get real content. > > So at least three requests are executed in sequence before the user > can see something. It is kind of expensive. > > Technically, in the very first request, the server already knows user > browsers' type, is that feasible to: > combine 1), 2) and 3) together or > combine 1) and 2) together or > some other consideration > > Would like to hear your opinions. > > Thanks > > --Michael > > -- > 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]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- 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.
