Hi Ron!

On 28 Mär 2014, Ron Wheeler wrote:

> Have you tried increasing the JVM memory past
> 
> MAVEN_OPTS="-Xmx1536m -Xms512m -XX:MaxPermSize=512m"
> MAVEN_OPTS="-Xmx1280m -Xms256m -XX:MaxPermSize=768m"
> 
> You could try something extreme (-Xmx8g ) and see if that changes anything.

Well, I should have added, that it was working fine with "-Xmx1024m
-Xms256m -XX:MaxPermSize=512m" recently. Since then I did a minor
restructure of the project and updated maven from 2.2.1 to 3.1.1. So I
thought the required memory wouldn't be much more.

> -Xms512m is not very useful in this case and you can omit it or make it the 
> same as -XMXnnn.
> Make sure that you allow enough(???) space after you allocate MaxPermSize.
> 
> MAVEN_OPTS="-Xmx8g -XX:MaxPermSize=768m"
> 
> 
> Did you notice that it took longer to run out  of memory with the higher 
> settings?
> If not, then I may be barking up the wrong tree and you might have to 
> change JAVA_OPTS to affect the memory allocation.
> If it did, then you are heading in the right direction but have not gone 
> far enough yet.

I tried with 8GB and now it was running for more that 4 hours. Than I
canceld it because the machine was only swapping and progress was very
low. (There were only 8GB physical RAM available on the system.)

With 4GB I got the usual OOM error. Can't say if it ran longer. If it
did, it wasn't that much longer. About 15min or so.

The point is: with maven 2.2.1, m-javadoc-p 2.8 and only minor changes in
the project layout it was running fine with 1GB. Now it needs at least
more than 4GB. There must be something wrong.

Any more ideas?

- martin

Attachment: signature.asc
Description: PGP signature

Reply via email to