Re: Why the GWT complier used so much memory?

Good to know, I'm using Mojo's maven plugin, so that would explain the default of localWorkers = 4. 

On Friday, September 14, 2018 at 10:05:23 AM UTC-3, Thomas Broyer wrote:

On Friday, September 14, 2018 at 2:25:44 PM UTC+2, Andrew Somerville wrote:

To your point, regarding tuning the localWorkers parameter, I get significant speedup going from the default of 4 localWorkers down to 2. (i5-4460 Desktop CPU, 500 GB SSD and 32 GB of RAM). It doesn't matter what I set the heap limit to, the compilation appears to be memory bandwidth limited, or perhaps GC bandwidth limited. 

Note that from GWT's side the default for localWorkers actually is 1, it's the gwt-maven-plugin(s) that use the number of CPUs of the machine as the default value (and always pass an explicit -localWorkers parameter to GWT)

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.