Re: 3.2 builds grind to a halt
Re: 3.2 builds grind to a halt
- Subject: Re: 3.2 builds grind to a halt
- From: Jens Alfke <email@hidden>
- Date: Tue, 29 Sep 2009 15:42:00 -0700
On Sep 29, 2009, at 2:21 PM, Steve Mills wrote:
Yeah, that prevents the endless grinding. 2 is a bit wimpy. 8 was
fine. 12 overwhelms it. I'll try 10 later. But I *hate* having to
hack my system this way - it should just work out of the box.
Xcode's default number of parallel builds is usually the same as the
number of CPU cores. (Since compilation is CPU-bound, having more
parallel tasks than CPUs usually doesn't help.)
In your case that would be 8 parallel tasks; if you've been using more
(you said 15?) I would imagine that you customized this setting
sometime in the past, so your Xcode setup wasn't out of the box before
the upgrade, either.
I haven't noticed GCC using more than about 120MB per process, for
small-to-medium-size files. I would imagine the RAM usage depends on
the complexity of the code and the number of headers; do you have a
huge precompiled header?
—Jens _______________________________________________
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