Re: XCode Compiling Threads
Re: XCode Compiling Threads
- Subject: Re: XCode Compiling Threads
- From: Bill Bumgarner <email@hidden>
- Date: Sun, 18 Jan 2009 20:48:42 -0800
On Jan 18, 2009, at 6:21 PM, Romain Marucchi-Foino wrote:
Hummmm why do you think?
Of course to speed up the compilation process...?!?!?!?
Because, of course, if something is slow, spawning more threads is
clearly the answer!
Since you seem to desire to talk on tuning Xcode to your compilation
needs yourself, I would suggest considering the following details
prior to determining the appropriate # for the expert preference.
- C, C++, ObjC or ObjC++.
All four tend to have radically different CPU and I/O requirements.
- if C++, STL or no? Lots of header file magic?
The style of C++ coding can radically change the compiler's resource
utilization
- precompiled headers? Many? Few? Big? Small?
PCHs can be massive and require much memory for the compiler to
consume. Or not. Depends on your project.
- optimization level?
Optimizations can cause the compiler to eat CPU and/or memory.
- doing anything else on the machine? Expect it to be responsive at
all?
Compilation is in a competition for resources. Turn up the # of
compiler processes can lead to system unresponsiveness
- how much memory in the system?
Gotta balance this with the above. Too little and 1 compiler at a
time doing C++ will be optimal. Boatloads o' memory -- great, but
then you'll likely be in contention for disk I/O.
Bottom line: Don't turn the dial up too much. If you do, you'll run
out of memory and the compilers will start paging. As soon as paging
happens, performance will suffer hugely.
b.bum
_______________________________________________
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