It also seems to be a time-issue.
I would like to see these numbers over, let's say, 10 runs. (OS and JDK
the same of course)
One thing worth investigating is if the buildplan related instances can be
cleaned up.
thanks,
Robert
Op Wed, 18 Mar 2015 11:19:33 +0100 schreef Jörg Schaible
<joerg.schai...@swisspost.com>:
Hi,
it seems to get my standard complaint about every new Maven version, but
we're currently stuck to Maven 3.0.5. One reason is the vast memory
usage of
any later version.
We have currently ~450 projects in the reactor, now compare the results
of a
simple validate:
Maven 3.0.5:
============ %< ==============
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 19.312s
[INFO] Finished at: Wed Mar 18 10:50:10 CET 2015
[INFO] Final Memory: 323M/1106M
[INFO]
------------------------------------------------------------------------
============ %< ==============
Maven 3.3.1 (and 3.2.5):
============ %< ==============
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 54.811 s
[INFO] Finished at: 2015-03-18T10:44:44+01:00
[INFO] Final Memory: 1806M/2731M
------------------------------------------------------------------------
============ %< ==============
Understandably the situation worsens if you actually try to build.
Cheers,
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
