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
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
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
Are you sure that you need the 2mb stack? I seem to recall there was
a problem a while back with stack overflows resulting in some people
suggesting large stacks. I think that's been fixed now.
Are you using a 32 or 64 bit JVM?
What are the exact compiler and JVM arguments you are using?
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
Yikes, that's a lot of memory!
I missed the note regarding x86 in the OP, so that puts you on a
32bit JVM.
Have you thought about renting a High Memory EC2 instance over at AWS
for a couple of hours?
C.
On Dec 15, 2:06 pm, Lukas Herman herni...@gmail.com wrote:
SOYC option on large project
