Sorry for taking so long to answer, but I haven't seen your post before. We haven't yet done any larger performance test, but it is very acceptable. Yesterday, in a first no-brainer attempt of GWT.runAsync(), I've managed to get a 650K initial download and then a separate file per module (for now, modules varies from few K to 180K). I'll still try to reduce both the initial download and the modules. It does takes more time to compile now. That's an issue to me as I can't use the built-in server: we use EJB, so there's an external server. Whenever anything changes in RPC (params, methods, even classes) we need to recompile :-/ I still didn't implement gzip compression, but hope things can get much better... Ah, about IE6: as our app is targeted to late 2010, we won't support IE6 \o/ -- Luis Fernando Planella Gonzalez
On 16 nov, 12:19, Bakul <[email protected]> wrote: > Hi, > > Our app, 50 -55 % done so far, for one browser is nearly 1.6 MB > without gzip. And it has nearly 70 -80 RPC calls. > > Luis, Question for you: > As you said your app is 2.1 MB of obfuscated, how is the preformance > and does it has any issue? > > Question to all: > What is the max size that of GWT one module that a browser can handle > without any issue, specially IE 6, in our case :-( ? > > Thanks, > Bakul. -- 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.
