10:17 a.m.
All,
I tried telling maven to use all my cores (8 if you count hyper-threaded cores) and
I've seen a 33% reduction in build times. Here's my results:
./build.sh clean install -DskipTests 3:43
./build.sh clean install -DskipTests -T 4 2:57
./build.sh clean install -DskipTests -T 8 2:30
I'm using an SSD, so YMMV.
However, there are 4 plugins that are not marked as @ThreadSafe, so i'm not sure how
safe this is.
[WARNING] org.apache.maven.plugins:maven-help-plugin:2.2 (Can't find an issue for this
yet)
[WARNING] org.codehaus.mojo:buildnumber-maven-plugin:1.2 (Claims to be fixed in 1.2:
http://jira.codehaus.org/browse/MBUILDNUM-13)
[WARNING] org.codehaus.mojo:xml-maven-plugin:1.0 (Unresolved:
http://jira.codehaus.org/browse/MOJO-1709)
[WARNING] org.kuali.maven.plugins:properties-maven-plugin:1.5.3 (Unresolved:
http://jira.codehaus.org/browse/MOJO-1677)
For more info on parallel maven builds:
https://cwiki.apache.org/MAVEN/parallel-builds-in-maven-3.html
Has anyone else experimented with this feature?
Paul.
--
Paul Robinson
Web Service Transactions Lead
paul.robinson(a)redhat.com
JBoss, a Division of Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors: Michael Cunningham (USA), Brendan Lane (Ireland), Matt Parson
(USA), Charlie Peters (USA)
10:25 a.m.
New subject: Parallel maven build: 33% improvement
I do experiment lots with this feature :-)
also reason why we currently have just 4 non @ThreadSafe plugins in our
build...
Only problem I found with this was that arquillian tests usualy behave
quite strange.
so if you do paralel build with -DskipTests then this is great but for
actual testing it is not that good.
I usually do -DskipTests -T4 and then just run part of testsuite that i am
interested in.
Also you can use -T 4C which will tell him to use 4 real cores not just
logical ones.
But this config really depends on project & hardware you are on.
--
tomaz
On Mon, Mar 25, 2013 at 4:17 PM, Paul Robinson <paul.robinson(a)redhat.com>wrote:
All,
I tried telling maven to use all my cores (8 if you count hyper-threaded
cores) and I've seen a 33% reduction in build times. Here's my results:
./build.sh clean install -DskipTests 3:43
./build.sh clean install -DskipTests -T 4 2:57
./build.sh clean install -DskipTests -T 8 2:30
I'm using an SSD, so YMMV.
However, there are 4 plugins that are not marked as @ThreadSafe, so i'm
not sure how safe this is.
[WARNING] org.apache.maven.plugins:maven-help-plugin:2.2 (Can't find an
issue for this yet)
[WARNING] org.codehaus.mojo:buildnumber-maven-plugin:1.2 (Claims to be
fixed in 1.2: http://jira.codehaus.org/browse/MBUILDNUM-13)
[WARNING] org.codehaus.mojo:xml-maven-plugin:1.0 (Unresolved:
http://jira.codehaus.org/browse/MOJO-1709)
[WARNING] org.kuali.maven.plugins:properties-maven-plugin:1.5.3
(Unresolved: http://jira.codehaus.org/browse/MOJO-1677)
For more info on parallel maven builds:
https://cwiki.apache.org/MAVEN/parallel-builds-in-maven-3.html
Has anyone else experimented with this feature?
Paul.
--
Paul Robinson
Web Service Transactions Lead
paul.robinson(a)redhat.com
JBoss, a Division of Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors: Michael Cunningham (USA), Brendan Lane (Ireland), Matt Parson
(USA), Charlie Peters (USA)
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
10:27 a.m.
I've done few tests with this in the past on the JBossWS project and
basically came to the conclusion that real improvement from parallel
execution would have come only from running multiple integration tests
at the same time (given my integration testsuite module run is much
longer then the rest of the build), so I preferred starting to use the
surefire parallel test execution instead.
Depending on how the project is split into modules, the maven 3 parallel
execution might still help, cxf for instance builds in parallel here (-T
4) in quick and reliable way on my i7 M 620.
Cheers
Alessio
On 03/25/2013 04:17 PM, Paul Robinson wrote:
All,
I tried telling maven to use all my cores (8 if you count hyper-threaded
cores) and I've seen a 33% reduction in build times. Here's my results:
./build.sh clean install -DskipTests3:43
./build.sh clean install -DskipTests -T 42:57
./build.sh clean install -DskipTests -T 82:30
I'm using an SSD, so YMMV.
However, there are 4 plugins that are not marked as @ThreadSafe, so i'm
not sure how safe this is.
[WARNING] org.apache.maven.plugins:maven-help-plugin:2.2 (Can't find an
issue for this yet)
[WARNING] org.codehaus.mojo:buildnumber-maven-plugin:1.2 (Claims to be
fixed in 1.2: http://jira.codehaus.org/browse/MBUILDNUM-13)
[WARNING] org.codehaus.mojo:xml-maven-plugin:1.0
(Unresolved: http://jira.codehaus.org/browse/MOJO-1709)
[WARNING] org.kuali.maven.plugins:properties-maven-plugin:1.5.3
(Unresolved: http://jira.codehaus.org/browse/MOJO-1677)
For more info on parallel maven builds:
https://cwiki.apache.org/MAVEN/parallel-builds-in-maven-3.html
Has anyone else experimented with this feature?
Paul.
--
Paul Robinson
Web Service Transactions Lead
paul.robinson(a)redhat.com <mailto:paul.robinson@redhat.com>
JBoss, a Division of Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors: Michael Cunningham (USA), Brendan Lane (Ireland), Matt Parson
(USA), Charlie Peters (USA)
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Alessio Soldano
Web Service Lead, JBoss
4050
days inactive
4050
days old
2 comments
3 participants
participants (3)
-
Alessio Soldano -
Paul Robinson -
Tomaž Cerar