I've tried setting compiler.stackMode=native and I gained 30 seconds for a single permutation, I don't need it during development so I now a compiles takes around 80/90 seconds.
Now I'm trying to implement the IncrementalGenerator interface on my generators but GeneratorContext.isGeneratorResultCachingEnabled() seems to be always false. 2012/6/10 Ray Cromwell <[email protected]> > looks like you have compiler.stackMode = emulated. It won't solve your > problem, but it should shave off some time to set it to 'native'. One > thing puzzles me is even the linker stage is taking 15 seconds for > you. That stage doesn't really do much but write files and create the > nocache.js script. There might be some degenerate issue there. Seems > like a significant amount of time is spend running RPC generators and > ClientBundle, even though it is not supposed to. > > -Ray > > > On Sat, Jun 9, 2012 at 11:54 PM, Stefano Ciccarelli > <[email protected]> wrote: > > The full compile takes ~16 minutes for 8 permutations. > > > > About the SuperDevMode the first compile takes ~260 seconds for 2 > > permutations, the subsequent compiles takes from 120-160 seconds each (1 > > permutation). > > > > The speedtracer.html file is attached. > > > > I have 4gb of ram and I'm using -Xmx1024m. > > > > I'm sure the performance will improve, the real problem now is that it > is a > > pain to use with gwt-rpc because I have to deal with generated *.gwt.rpc > > files. > > > > -- > > Inviato con Sparrow > > > > Il giorno sabato 9 giugno 2012, alle ore 21:26, Ray Cromwell ha scritto: > > > > BTW, can you send me the speedtracer.html file in your > > /tmp/*codeserver/* directory? > > > > > > On Fri, Jun 8, 2012 at 1:41 PM, Stefano Ciccarelli > > <[email protected]> wrote: > > > > My app is 600000 lines of code and compiles in 120 seconds: a lot of > > uibinder, a lot of classes in rpc, gin… so a lots of generators. > > > > -- > > Sent with Sparrow > > > > Il giorno venerdì 8 giugno 2012, alle ore 22:38, Ray Cromwell ha scritto: > > > > I just checked again, one of the internal apps we are trying > > SuperDevMode against has about 400,000 lines of code and combines in > > about 7-8 seconds. So maybe your app has 6x as much code? If not, it > > gives us a clue that perhaps there's some other edge condition causing > > the compile to be slow. > > > > -Ray > > > > > > On Fri, Jun 8, 2012 at 12:09 PM, Ray Cromwell <[email protected]> > > wrote: > > > > How big is your app? (KLOC) Internally, we'd had success with <10s > > refresh on some fairly largish apps. I'm wondering if something else > > isn't going on. Note that the first compile usually takes long, but > > subsequent ones are faster. Are you using UiBinder? One issue could be > > generators using too much time. > > > > > > On Fri, Jun 8, 2012 at 11:21 AM, Jens <[email protected]> wrote: > > > > Just to finish this off in case anyone else has the same problem - > > this was fixed in r11031. > > > > https://code.google.com/p/google-web-toolkit/source/detail?r=11031 > > > > > > > > Thanks for the info. I had the same problem but now it works. Now lets > hope > > the compilation process will become a lot faster in the future. A single > > permutation of our app compiles on the code server in ~45 seconds and > thats > > not really acceptable during development compared to the "classic" > DevMode. > > > > -- J. > > > > -- > > http://groups.google.com/group/Google-Web-Toolkit-Contributors > > > > > > -- > > http://groups.google.com/group/Google-Web-Toolkit-Contributors > > > > > > -- > > http://groups.google.com/group/Google-Web-Toolkit-Contributors > > > > > > -- > > http://groups.google.com/group/Google-Web-Toolkit-Contributors > > > > > -- Nel mondo esistono 10 categorie di persone, quelle che capiscono il binario e quelle che non lo capiscono. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
