We have a fairly large single GWT project that we feel has out-grown itself
at this point. It's setup in a way where we could split it out into a
collection of smaller projects (though this is not a simple task). What
I'm looking to find out: does compile time of large GWT projects scale
Just curious, how long is your compilation time? I think our GWT project
is relatively big (well over 100,000 lines of client-side Java source code;
the split point report shows total generated code size about 1.5MB), and it
compiles 5 permutations in about 70 seconds on my system. (We
I assume with multiple projects you mean multiple apps each having its own
html host page? I don't think you will gain a lot because at the end you
have to compile the same amount of source files regardless if its one big
project or 10 smaller projects.
If your app takes really that long to
On our build machine (which isn't the fastest thing in the world), it takes
40 minutes to run javac + build 18 permutations. Running the compileReport
on it, tie Full code size is just under 5MB.
And yes, multiple apps, each having their own html host pages. I was
thinking that splitting
To add. the permutation-0.js generated by the compileReport is 640MB.
And using cloc http://cloc.sourceforge.net/, we are at 200k lines of
code for java+xml (for uiBinder).
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To unsubscribe
On our build machine (which isn't the fastest thing in the world), it
takes 40 minutes to run javac + build 18 permutations. Running the
compileReport on it, tie Full code size is just under 5MB.
Sounds like your build machine is either really slow or CPU is not at 100%
during
Right. On a fast machine (Core i7 with a lot of RAM and using
-localWorkers 2), that should be maybe 5-10 minutes, not 40.
On Wednesday, February 5, 2014 11:23:11 AM UTC-8, Jens wrote:
On our build machine (which isn't the fastest thing in the world), it
takes 40 minutes to run javac +
It's a VM with 4 CPU cores (X5690 CPU, Xeon's are from Q1 2011), and 10GB
of ram. It looks like the 40 minute quote was doing with localWorkers=1.
On another build with localWorkers=3, the build time was 12 minutes 30
seconds.
It looks like on the GWT compile we set:
-XX:MaxPermSize=128M
That's a lot better than 40 minutes. It would get even better if there
wasn't a VM in the mix.
On Wednesday, February 5, 2014 11:44:35 AM UTC-8, James Wendel wrote:
It's a VM with 4 CPU cores (X5690 CPU, Xeon's are from Q1 2011), and 10GB
of ram. It looks like the 40 minute quote was doing
Splitting one project into several projects will dramatically increase the
compilation time and the total size of your code. There will be a lot of
duplicate work for GWT to do on each project, and each project will have to
import a lot of the same classes.
I would only recommend splitting out
Are you using a 64bit JVM ? My experience is that when you use 64bit on VMs
that it is about twice as fast as a 32bit version.
On Wed, Feb 5, 2014 at 9:53 PM, Jim Douglas jdou...@basis.com wrote:
That's a lot better than 40 minutes. It would get even better if there
wasn't a VM in the mix.
11 matches
Mail list logo
