Page 1 of 1

Transformation JVM Arguments default value

Posted: Tue Mar 31, 2020 3:29 pm
by ckabstein
Hello,

Since we have several large documents that require a lot of memory when transformed, we have come across the error message "java.lang.OutOfMemoryError: GC overhead limit exceeded".
Changing the JVM Arguments value in the transformation's Advanced tab from -Xmx384m to -Xmx1g or -Xmx4g helped immediately to solve this error.
Would it make sense maybe to increase the default value of this option to at least -Xmx1g so that most documents could run without running into this issue?

Best,
Christina

Re: Transformation JVM Arguments default value

Posted: Thu Apr 02, 2020 9:07 am
by Radu
Hi Christina,

Thanks,you are quite right, I added an internal issue for this.
The problem might be that if we increase the default allocated memory on certain computers the transformation might not start at all if the operating system cannot allocate that much memory for the process. But these cases may be quite rare. We'll discuss this in an internal meeting.

Regards,
Radu

Re: Transformation JVM Arguments default value

Posted: Sun Apr 05, 2020 2:13 pm
by chrispitude
We use a 3GB default for the transformations that our writers run on their laptops (8GB memory).

Re: Transformation JVM Arguments default value

Posted: Fri Nov 20, 2020 1:03 pm
by Radu
Hi Christina,

We released Oxygen 23 yesterday. With Oxygen 23, default and newly created transformation scenarios no longer have a hardcoded -Xmx memory setting in them. You can still specify the -Xmx in each scenario but if you do not we choose what's best, usually meaning one gigabyte of memory allocated by default instead of the old 512 megabytes.

Regards,
Radu

Re: Transformation JVM Arguments default value

Posted: Fri Nov 20, 2020 1:08 pm
by ckabstein
Hi Radu,

This is a good solution. Thanks!

Best,
Christina