• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Distributed Builds
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Distributed Builds


  • Subject: Re: Distributed Builds
  • From: Dix Lorenz <email@hidden>
  • Date: Mon, 14 Mar 2005 23:46:55 +0100


On 14.03.2005, at 18:39, Thomas Davie wrote:

That's exactly my point - if you're compiling lots of files then you don't care, it doesn't matter if you spend a little bit of CPU duplicating effort at the end.

Agreed so far.

What does matter is if you have only 2 files to compile, and you would normally say, I'll build the first one, the second one gets shipped off. You make the assertion that it would be faster to compile both files locally rather than ship one off. If this is the case, then we can ship one off, and compile one locally, when that finishes, compile the one we shipped off locally... If it finishes first, then woo yay we've cut compile time, if it doesn't finish first then we would have been faster distributing it anyway.

Let's start from one file. This happens very often when I edit a file and I hit compile, just to see if the syntax is correct. My point is that compiling this one file is probably in most setups faster to compile locally than remotely. Going from there and having a dual-proc machine I would think that compiling 2 files is still faster to compile both locally than remotely. But actually exactly 2 files is a pretty rare occurence. After that using the remote machine will benefit the compile time.


I know that in my setup I would like the local machine to get the first jobs. But in my setup the remote machine always get the first jobs and I would like to change that. I don't see a way to do that and if there isn't I would think it is a pretty small change and would benefit most users. Changes like "if a machine is busy with file A but some other machine is finished get it to the idle machine, maybe it is faster" is a lot more complicated that just being able to specify which machine should handle builds first...

Dix

_______________________________________________
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


  • Follow-Ups:
    • Re: Distributed Builds
      • From: Dave Camp <email@hidden>
References: 
 >Distributed Builds (From: Dix Lorenz <email@hidden>)
 >Re: Distributed Builds (From: Rob Frohne <email@hidden>)
 >Re: Distributed Builds (From: Thomas Davie <email@hidden>)
 >Re: Distributed Builds (From: Dix Lorenz <email@hidden>)
 >Re: Distributed Builds (From: Thomas Davie <email@hidden>)
 >Re: Distributed Builds (From: Dix Lorenz <email@hidden>)
 >Re: Distributed Builds (From: Thomas Davie <email@hidden>)

  • Prev by Date: Re: Saving and Importing Targets in Xcode 1.5 Projects
  • Next by Date: Re: Distributed Builds
  • Previous by thread: Re: Distributed Builds
  • Next by thread: Re: Distributed Builds
  • Index(es):
    • Date
    • Thread