Re: GWT 2.5 compiler is running out of memory

On Friday, February 1, 2013 6:02:11 PM UTC+1, dhoffer wrote:

Yes using -Dgwt.jjs.permutationWorkerFactory=com.google.gwt.dev.ThreadedPermutationWorkerFactory fixed the problem!  Everything compiles fine now.

With that set I was able to remove <localWorkers>...but just wondering what <localWorkers> means when using threads.  Does that control the number of threads, have no effect?

localWorkers controls the number of "workers" (defaults to 1 in the Compiler, but gwt-maven-plugin sets it to Runtime#availableProcessors() by default); the workers are created by a factory. The default factory (ExternalPermutationWOrkerFactory) spawns external processes (looking at the code, you can override the JVM opts the the subprocesses by setting the gwt.jjs.javaArgs system property, and even the java command –to use a different JVM for instance– using the gwt.jjs.javaCommand system prop).

Google probably uses a custom factory the distribute the load to a cluster, in this case the localWorkers is not used (if the factory returns false from its isLocal() method).

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.