Kai Backman wrote:
Thanks for the detailed answers to both of you! :-)
On 10/30/06, Jens-Heiner Rechtien <[EMAIL PROTECTED]> wrote:
About 16 machines, from 2 to 8 processors, plus a number of special
Looking at the machine list, are they dual or single core CPU's?
The Sun-Fire 890 (fileserver) has dual core CPU's, the rest of the
machines has single cores CPU, but at least two of them.
Fileserver: Sun-Fire 890 with 4 double core 1500 MHz Ultra-Sparc IV
processors, 16 GBytes RAM, Solaris 10
So I assume this is the fileserver shared for the whole site? Or do
you have a separate build infrastructure set up?
This file-server is not used as server for CWS builds by developers. But
developers access this system for fetching pre-compiled stuff. Developer
CWSs are stored on a separate system.
> - What is the utilization of the cluster? Ie. How much paralellism are
> you able to extract from the build? 75% 80%?
In the beginning of a build the parallelism is kinda restricted because
prerequisites need to be build. Later the parallelism is pretty good,
most of the time are all clients (nodes) are doing something. When
creating package set (a significant part of the total build time) the
parallelism is perfect.
I don't understand the last sentence. What is "creating package" and
by perfect do you really mean 100% (which sounds a bit too high)..
During release times we create about a 1000 or so installation sets per
milestone (think of all the languages OOo has, and the different ways
OOo and StarOffice comes to you). This needs a lot of computational
power and all our clients (nodes) are busy creating them. Each
installation set can be created in parallel with all the other
installation sets, thus for a few hours all clients are permanently busy.
Heiner
--
Jens-Heiner Rechtien
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
