Re: : Distribute to local machine too?
Re: : Distribute to local machine too?
- Subject: Re: : Distribute to local machine too?
- From: leenoori <email@hidden>
- Date: Fri, 20 Oct 2006 15:07:46 +0200
El 20/10/2006, a las 6:01, Steve Mills escribió:
Damn it Jim, I'm a developer, not a doctor. I want to click a
button that says "distributes builds" and click another button that
says "use all available machines on the network". I don't want to
read a bunch of low-level reference manuals or have to become a
Unix expert. I already have enough stuff to do.
I agree that it would be good if Xcode could at the very least
distribute to the local machine according to the number of available
cores. For example, on a machine with two dual-core CPUs (four cores
in all) I think Xcode should use one core for scheduling (to other
hosts on the network as well as the local machine) and the other
three cores for compiling.
I remember a few weeks ago when I got my Mac Pro and was so excited
that my full build was now 10 minutes on it instead of 22 minutes
on 2 G5's and a G4. Then I turned on distributed builds so the
Intel iMac in the other room could get in on the action. Man was I
surprised that the time went back down to about 20 minutes when I
did that. That's when I discovered that builds will *only*
distribute to the other machines and the host machine goes mostly
to waste.
This is the reason why Apple has recommended (in posts to the this
list, I believe) that in such a set up you use the slower machine to
distribute the builds to the other, faster machines. But obviously
that isn't ideal because it would mean jumping through hoops to
invoke xcodebuild on the other machine...
_______________________________________________
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