Re: GWT compilation performance

  have you compared the performance when switching from HDD to SSD drive ?

For DevMode I can't give any numbers but IMHO it feels faster to reload the app in DevMode. But don't expect a large difference.

For compiling an app to JavaScript using the GWT compiler you do not gain that much from an SSD. Just compiled one of the larger apps and it has taken

Workspace + tmp folders on HDD: ~270 seconds

Workspace + tmp folders on SSD: ~260 seconds

Workspace + tmp folders on RamDisk: ~245 seconds (does not include time to copy things into ram disk)

So its not a big difference. 

During compilation the most benefit you get is when you can compile all your permutations at the same time. In the above example I used -localWorkers 4 on a Quad Core CPU with hyper threading. Increasing localWorkers to 8 to fully use hyper threading and get a constant 100% workload on each core/virtual core the time dropped to ~250 seconds in case of HDD. So make sure your build machine uses all cpu power available and then use distributed builds on multiple build machines if you have a large number of permutations.

https://code.google.com/p/google-web-toolkit/wiki/DistributedBuilds

-- J.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.