Re: Compilation server options
Re: Compilation server options
- Subject: Re: Compilation server options
- From: Greg Guerin <email@hidden>
- Date: Tue, 5 Dec 2006 14:10:38 -0700
Shai Shasag wrote:
>We thought of two options:
>
>1) Get a Xserve and use it both as the main batch compiler and also
>share it for distcc.
>
>2) Get 5 Mac minis. Share them all for distcc. One of these will run
>the big compiling jobs, using the others through distcc.
>
>Both options cost the same but which will get us faster compiles?
I think you'll have to measure, or at least measure and extrapolate, in
order to answer that.
There may not even be one answer. It might be that one configuration is
faster for day-to-day use and the other is faster for big-batch use. What
then?
Also, Apple's notes on Distributed Compilation says that distcc is good up
to about 10 nodes, but beyond that DNB is better. So the answer might also
change depending on how your group scales up or down, e.g. you add
developers in a year, or you divide into sub-projects in a year. It could
be that faster compiles now turns into slower compiles next year.
Personally, I'd also consider how each config degrades. If the Xserve
dies, it's working at 0%. If a mini dies, the cluster is still working at
80%. Nothing kills productivity faster than getting 0 compiles per hour.
Then again, reliability statistics may favor the Xserve's MTBF, but there's
also MTTR to consider.
-- GG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden