There's a known issue, in at least Sun's JDK and OpenJDK, where ClassLoader lookups are O(N) of the entries on the classpath. GWT can perform a very large number of lookups, so it's especially affected. One way to workaround this is to collapse multiple classpath entries into a single jar or directory. You can see very significant improvements in both compilation speed and in dev mode.
On Fri, Dec 23, 2011 at 12:51 PM, Joshb <joshblin...@gmail.com> wrote: > Hi, I have a few questions surrounding ResourceOracleImpl.onRefresh. > Please excuse my ignorance in advance. > > I have a rather large GWT project, with a lot of dependencies. Currently, > it takes approximately 20-30 seconds to refresh the browser (my machine is > an i7 with 8GB of RAM). It seems that the time is taken up traversing > through the entire classpath each time I press refresh, and my question is > why this is necessary. > > > - Could the GPE theoretically listen for changes to the classpath and > update the resource oracle specifically when they change (eliminating the > need to refresh when browser-refresh is called)? > - Theoretically, could the resourceOracle be instructed to only listen > to GWT based projects (some sort of whitelist)? > > I recognize that perhaps some of these issues could have been avoided with > better architecture on my part, but we have a pretty large application that > isn't going to be refactored anytime soon. > > Thanks for your time and consideration. I hope this makes some sense, > > Josh > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
