[
https://jira.nuxeo.com/browse/NXBT-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=109430#comment-109430
]
Mathieu Guillaume commented on NXBT-356:
----------------------------------------
For the first run of tests, I did an offline build (with tests) of
nuxeo-features.
Default JDK used was Sun's Java 6, with MAVEN_OPTS="-Xmx1024m
-XX:MaxPermSize=256m".
* Server 1: 2x4 cores (Intel Quad Core i7 870 @ 2.93GHz), 16GB RAM
Compile times: 7m39, 7m46, 7m53
Alternative test - double maven memory: 7m49
Alternative test - OpenJDK6: 10m06
Alternative test - OpenJDK7: 7m52
Alternative test - maven 3: 7m40
* Server 2: 1x4 cores (Intel Quad Core Q6600 @ 2.40GHz), 4GB RAM
Compile times: 12m09, 12m59, 13m56
Alternative test - double maven memory: 12m46
Alternative test - OpenJDK6: 14m39
* Server 3: 1x4 virtual cores (AMD Quad Core Opteron 2374 HE @ 2.20GHz), 4GB RAM
Compile times: 13m58, 14m21, 14m08
Alternative test - double maven memory: 13m23
Alternative test - OpenJDK6: 21m48
Alternative test - OpenJDK7: 14m33
* Server 4: 1x2 cores (Intel Core 2 Duo E6550 @ 2.33GHz), 2GB RAM
Compile times: 15m46, 16m42, 17m57
Alternative test - double maven memory: 34m49
Alternative test - OpenJDK6: 20m48
Conclusions:
- the default memory parameters are sufficient for build tasks, increasing
memory doesn't benefit the build times (and hurts them in the case of Server 4,
which has to use swap).
- build tasks seem to be pretty much only CPU-bound.
Alternate tests:
- OpenJDK6 is slower, there would be no benefit to switch to it.
- OpenJDK7 and maven3 don't significantly alter build times.
> Define a CI slave for performance
> ---------------------------------
>
> Key: NXBT-356
> URL: https://jira.nuxeo.com/browse/NXBT-356
> Project: Nuxeo ECM Build/Test Environment
> Issue Type: Task
> Components: Continuous integration
> Reporter: Julien Carsique
> Assignee: Mathieu Guillaume
>
> Slave build performances
> Currently the build on the Jenkins slaves is about the same time than on a
> dev laptop.
> => we can make better !
> It's true that a big part of the Jenkins slave are poor hardware (the dwarf).
> Before taking any decision, we should probably do some profiling to see
> exactly what are the real impacting factors :
> test build on a bigger CPU (like Octo)
> use RAMFS to speedup I/O
> tweak compile options ?
> test on big RackSpace VMs
> => based on that we will be able to define what kind of Build slaves we need
> (then we will have to see what we can host internaly and what must be
> external)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
