Upgrading to mvn-3.6.2?


Robert Varga
 

Hello,

maven-3.6.2 is out and it contains major improvements in startup time (i.e. figuring out what to do).

Local testing of 'mvn help' on controller yields the following:

nite@nitebug : ~/odl/controller on master $ time ~/local/apache-maven-3.5.4/bin/mvn help >/dev/null
real 0m7.591s
user 0m33.862s
sys 0m0.806s
nite@nitebug : ~/odl/controller on master $ time ~/local/apache-maven-3.6.0/bin/mvn help >/dev/null
real 0m5.505s
user 0m22.748s
sys 0m0.691s
nite@nitebug : ~/odl/controller on master $ time ~/local/apache-maven-3.6.2/bin/mvn help >/dev/null
real 0m3.436s
user 0m13.337s
sys 0m0.522s
i.e. saving 20 seconds (60%) of CPU time and 4 seconds of wall time (55%) from controller build.

Looking at autorelese, this startup time now takes:

00:40:33 Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z)
00:40:33 Maven home: /w/tools/hudson.tasks.Maven_MavenInstallation/mvn35
00:40:33 Java version: 1.8.0_222, vendor: Oracle Corporation
00:40:33 Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.222.b10-0.el7_6.x86_64/jre
00:40:33 Default locale: en_US, platform encoding: UTF-8
00:40:33 OS name: "linux", version: "3.10.0-957.12.2.el7.x86_64", arch: "amd64", family: "unix"
00:40:34 [INFO] Error stacktraces are turned on.
00:40:34 [INFO] Scanning for projects...
00:41:19 [WARNING]
i.e. 45 seconds of wall time @jenkins. Local testing (with Java 11, sorry) shows:

nite@nitebug : ~/odl/autorelease on master $ time ~/local/apache-maven-3.5.4/bin/mvn help >/dev/null
real 0m38.492s
user 3m48.811s
sys 0m2.093s
nite@nitebug : ~/odl/autorelease on master $ time ~/local/apache-maven-3.6.0/bin/mvn help >/dev/null
real 0m27.265s
user 2m46.288s
sys 0m1.512s
nite@nitebug : ~/odl/autorelease on master $ time ~/local/apache-maven-3.6.2/bin/mvn help >/dev/null
real 0m10.237s
user 0m50.400s
sys 0m1.550s

Would it not make sense to switch to maven-3.6.2?

Regards,
Robert

Join integration-dev@lists.opendaylight.org to automatically receive all group messages.