On Monday, April 3, 2017 at 10:09:06 AM UTC+2, Thomas Buckel wrote: > > Hi all, > > I've been working on an enterprise GWT app for the last few years. It has > grown and will grow quite a bit and compile times (DevMode, SuperDevMode) > are becoming a real pain point for the developers. > > A SuperDevMode initial compile takes about 50sec with GWT2.7/Java7 on a > 2.6GHz i7 Macbook Pro when SuperDevMode starts. Even a simple change of > just a label takes 5sec as reported by GWT plugin on refresh. Performance > is worse on Windows machines. > > As suggested in many examples, there we use a Dev profile/.gwt.xml with > only one permutation, draft compile and optimizationLevel=0. SDM has 3GB > heap size. Client and Server code are in one Maven module with quite a few > libraries (server side). We use an exploded but doubt that would affect the > GWT compile times. > > Are there any other optimisations I can try or this this the kind of > performance during development we have to live with? >
Things I would try: - GWT 2.8; SDM will likely be faster - removing server-side dependencies from GWT classpath; which means with Maven splitting client and server code into separate modules. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
