Re: Distribute to local machine too?
Re: Distribute to local machine too?
- Subject: Re: Distribute to local machine too?
- From: Shaun Wexler <email@hidden>
- Date: Wed, 18 Oct 2006 20:52:45 -0700
On Oct 18, 2006, at 11:16 AM, Dix Lorenz wrote:
On Oct 18, 2006, at 6:57 PM, Dave Camp wrote:
We've got a similar problem here. On a Mac Pro with distributed
builds enabled, the 4 Xeon cores site idle and send all the work
on two Intel iMacs on the network. It's completely backwards.
Is there some secret defaults setting that can be changed to fix
this?
If you find one, tell me, I have the same problem. I filed a bug
about this in January, the answer was "Engineering has determined
this issue behaves as intended." :-(
Ahem, hey DTS: engineering is wrong... this Just Doesn't Workâ˘.
The behavior was changed for 2.3-2.4, and whereas that might be fine
for a dedicated build farm of umpteen cores, so you can play games
while your build completes, most developers have only a few machines
and tend to use the baddest [Quad G5 / Mac Pro] as their workstation,
and would like to leverage the other stragglers to help out. The
localhost should leverage (available CPUs - 1) for distcc processes.
What's the point of the priority popup then, anyway?!!
Signed, another disgruntled former user of Xcode Distributed Builds.
--
Shaun Wexler
MacFOH
http://www.macfoh.com
Sarchasm \sar"chasm\, n. the void between the author of
a satirical witticism and the recipient who just doesn't get it.
_______________________________________________
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