Not much related to memory I think. Sure, more memory helps, but there are other things to check, the most important probably being:
1. reduce the DevMode classpath to the minimum necessary. One common mistake (which the GPE or "mvn gwt:run" do by default, but they technically cannot do otherwise due to limitations of Eclipse and Maven) is to include server-side dependencies in the classpath for the DevMode: server-side code are loaded from the WEB-INF, like in any webapp, they don't need to be on the classpath for the servlet-container (you're not tweaking the classpath for Tomcat –or whatever your servlet container– when deploying a new webapp, right?) 2. use a fast I/O: an SSD, or even a ramdisk. (honestly, I've never done that, but I've heard many people saying it really helps) -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/kB85FvhNU00J. 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.
