[
https://jira.nuxeo.com/browse/NXBT-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=109799#comment-109799
]
Mathieu Guillaume commented on NXBT-356:
----------------------------------------
Selenium tests on Chrome (note: can't be compared directly to Firefox tests as
the full suite isn't passing on Chrome).
- Server 1: 16m57, 13m42, 13m58
- Server 2: 19m11, 19m33, 21m15
- Server 3: 23m17, 23m30, 21m54
- Server 4: 20m33, 20m59, 22m31
CPU is having more impact than with Firefox, but not as much as for builds.
> 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
