Will you be giving the -XX:+UseCompressedOops option a try when on the 64-bit JVM? I'd be interested to hear about your experiences.
Good luck. C. On Dec 17, 6:20 am, Gerhard Davids <glacieredp...@gmail.com> wrote: > Hi, > > Thanks for all the responses. > The build tips surely helps Lukas. > > Yeah the whole 2m stack space issue may have been resolved but to be > perfectly honest I don't feel safe yet. > I have found that I will have to resort to upgrading to a 64bit os and > or JVM. > I dont really need the EC2 as I have a very decent build server that > can handle the load. > > Its just a shlep(and slow) to commit to our source control and get > from the server etc.. etc.. > > I'll post my experience once I have upgraded to 64 bit. > > Thanks again for the responses. > > On Dec 15, 4:06 pm, Lukas Herman <herni...@gmail.com> wrote: > > > > > SOYC option on large project takes immense amount of memory and hdd > > space. However, runAsync splitting is compiled properly without - > > draftCompile switch. > > I have ended with -Xmx32768m java memory for GWT Compiler using -soyc > > command line switch (i guess 8GB+ is sufficient). The generated files > > took over 2GB space on the hdd, and it took over 40 minutes to > > finish. > > There are 130 split points. > > Normal, production build takes less than 2 minutes per iteration. > > > Hope this helps. > > > Lucas > > > On 15 pro, 10:05, Gerhard Davids <glacieredp...@gmail.com> wrote: > > > > Hi Folks, > > > > I'm currently sitting with my hair in my hands. > > > > Before I ask my question I'll provide some info on the work I'm doing > > > related to the question: > > > > I am working on massive(MASSIVE) enterprise GWT[2.0] application. > > > The app currently consists of 3 java projects of which one is GWT(with > > > entry point) and the other two are common type of lib's used by the > > > main GWT app. The app also uses Ext-gwt[GXT] > > > > Now when compiling we use 2.1gig of Xmx and 2m of Xss -> Build Server. > > > This takes about 30 minutes on our build server(get it now? MASSIVE!) > > > > Righto, so here's the question : > > > > How can I speed up my local machine memory footprint? > > > I have set the project to compile only one permutation (ie8). > > > I provide 2m Xss and 1500(+/-) Xmx This still fails with > > > OutOfMemoryException and I cant provide it with more due to my x86 OS. > > > With GWT 1.7 i was still able to pull of a build locally albeit slow. > > > > DraftCompile is not an option as I want to do IE performance testing > > > with gwt 2.0 as well as soyc and runAsync. > > > > On the up side... I do get a partial soyc but i can't pump my war onto > > > apache because the compile never finishes. > > > I've read around and it seems i cant split the 3 projects as GWT > > > compilable modules that work as one. > > > > Any ideas? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
