Re: Slow link times
Re: Slow link times
- Subject: Re: Slow link times
- From: Alastair Houghton <email@hidden>
- Date: Tue, 12 Jan 2010 17:01:37 +0000
On 12 Jan 2010, at 16:38, Jens Alfke wrote:
> Right now I'm missing ZeroLink :(. On my 2008 MBP, I have a two-minute minimum turnaround time for building Chromium — i.e. if I open chrome.xcodeproj with the "chrome" target, build, then touch one source file and build again, that rebuild takes two minutes. Ouch. Compiling the changed file takes only a second; the great majority of the time is spent linking (with "checking dependencies" a close second.)
>
> This is almost entirely I/O bound. The CPU load is near zero. The same build process on my Mac Pro at work, which has a faster hard disk, takes less than half as long.
>
> I know, this is a very large C++ project, so linking is always going to be a chore. Does anyone have tips on how to optimize link times? Does it help to link subcomponents into static libraries and then link those together? (Actually I think Chrome is doing some of that already.)
It's very old-fashioned, but if you have the spare RAM, you could make yourself a ramdisk to hold the intermediate files. That's what I used to do back in the 90s...
A disk image might work also, depending on how much spare memory you have and on how well Apple has implemented the disk image stuff.
Just an idea... haven't tried it myself.
Kind regards,
Alastair.
--
http://alastairs-place.net
_______________________________________________
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