One thing you can try that I believe will be in GWT 2.3 is to set the experimental GWT flag -XenableGeneratorResultCaching. It gives a modest speedup if your app uses a lot of client bundles.
Thomas is referring to the new "PersistentUnitCache" class we've been working on. It isn't ready in GWT 2.3, but if you checkout GWT trunk, you can give it a try by adding -Dgwt.persistentunitcache -Dgwt.persistentunitcachedir=/tmp/<user> to your JVM args when invoking DevMode. It won't seem any faster the first time you start dev mode, but should be 40-50% faster on subsequent restarts. The initial build of all classes can be helped by trimming down your source path as Thomas says. One tool to help you do this is to run the compile report (add -compileReport to your command line), and then brows to the 'soyc' directory and pull up index.html in a web browser. Under compiler metrics you will find a list of all sources that were compiled, but remained unreferenced at the end of the build. Sometimes you can re-define your .gwt.xml module files to exclude sources from the build that are not needed. -- 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.
