Hi, I'm currently trying to migrate a big project at work from GWT 2.5.1 to 2.7.0 to test the new SDM.
Even if the recompile took 1-2 min on 2.5.1, the SDM was working with "-Xmx 1200m". It is already a lot of memory but was manageable. Now with 2.7.0-rc1, I have to increase it to "-Xmx 1800m" to avoid an OOM. Besides some bugs (https://github.com/ArcBees/GWTP/issues/614 or https://code.google.com/p/google-web-toolkit/issues/detail?id=4479), the incremental recompilation without modification works but it is still slow (~ 30 sec). The memory needed is too much for my machine, I keep swapping to a very slow disk :( And since we all have the same crappy laptop at work, the problem will be present for everyone working on this project. I guess the bump in memory is needed for the incremental compile to work correctly but what are the best ways to reduce it ? The project is not modular with a clean separation between client and server. So the SDM has all the libraries of the server in the classpath. If we split the client from server and reduce the classpath, can we expect a decrease in memory usage ? Or classes not used by the GWT module have no impact ? One of our RPC services uses Serializable so it generates a lot of code. Can it have an impact on memory usage too ? If that doesn't work, our only solution left is to divide in multiple GWT module and make something like turducken <http://fr.slideshare.net/RobertKeane1/turducken-divide-and-conquer-large-gwt-apps-with-multiple-teams> ? -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/4224704c-fc8c-493c-8f7a-b8c93357503e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
