Hi, I have just recently tried the code splitting functionality and to see the real benefits, I had to of course use the -compileReport flag on the compiler.
I split my code in just one place, and was amazed at the result on the report. It took only 3:26 minutes to compile (before that, my app took aprox. 2:40 mins to compile, and I must select just one browser and 2 languages: thus 2 permutations) Glad with the initial download gain, I started placing more split points along my code, in places similar to those. I didn't just pop GWT.runAsync() all over the place, mind you! When I compiled a report again to see the gain in initial loading, my report took 35 minutes this time to generate, and ended up with 2.9GB in size (48.000 small html files)! Ok, all this talk just to ask for this: Could it be done in the next version of GWT to be able to select the compile report type? In some cases all we need to see is the difference in Full code size and Initial Download size. So just a summary would be nice. Something like [-compileReport type] (like the [-workDir dir] flag) where type would be: - minimal : just the difference in code sizes - normal : not so much info as right now. maybe just the breakdown of the Initial and Leftover codes. - detailed : what it's doing right now Because my guess is that it's taking so long not because of the intel gathering, but because it is writing too many files on disk. Maybe you can attest this... and prove me wrong. -- 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.
