Re: Turning off the garbage collector for Xcode 3.0
Re: Turning off the garbage collector for Xcode 3.0
- Subject: Re: Turning off the garbage collector for Xcode 3.0
- From: Jens Alfke <email@hidden>
- Date: Fri, 1 Aug 2008 17:56:02 -0700
On 1 Aug '08, at 5:26 PM, email@hidden wrote:
other quarter of time was wasted by the garbage collector itself.
GC time isn't "wasted". Memory has to get freed one way or another.
The majority of it is time that would otherwise be spent in -retain, -
release and -dealloc calls; it just becomes more noticeable in a GC
environment because it's spent in a single place rather than being
spread out all over the code.
We have a big suspicion a generation of the mentioned snapshots gets
fixed in Xcode in the nearest future, since the odds are Apple does
not care about it and it does nothing in this direction, it makes
things even worse (Mac Pro just sucks on Xcode 3.2)
I can't figure out what that sentence says. In any case, did you
report this problem through Apple's bug reporter, including relevant
performance data like Shark samples? If you don't report it, they
might not know about it. (The fact that snapshots are involved sounds
really suspicious, since that shouldn't be happening unless you
manually take a snapshot.)
perhaps assuming serious projects (which contain lots of C++ source
files) are not being built using Xcode, but it is suitable/
applicable just for simple "Hello world!" applications.
Haha! That's cute. You should see some of the little toy hello-world
programs that get built with Xcode, such as Mail, Safari, Finder,
Final Cut, Quartz, Photoshop (and of course Xcode itself.)
The use of C++ not an indicator of a "serious" project. I've worked on
plenty of C++ code, and also plenty of "serious" code in other
languages, from Objective-C to Smalltalk to assembly code. I will
grant you that C++ is especially slow to compile because the
language's syntax is so complex, but that wouldn't affect Xcode,
rather the GCC compiler.
Th us, we would like to ask you whether we able to TURN OFF the
garbage collector and safe some processor resources for execution of
Xcode's frond end which does the real work.
Xcode's front end doesn't do the real work of building. That's done by
child processes, mostly gcc.
At the early beginning when Xcode 3.0 was beta and shipped within
Leopard seeds it was possible to turn off the garbage collector by
creation of special files in /etc or so, just can't recall exactly,
but it stopped working in one of seeds closer to the final one.
No, you can't disable it. But if it's presenting a performance problem
during builds, something's really wrong, because build time should be
dominated by GCC and related tools, not the IDE itself. As I said,
file a bug report; posting some samples here might be interesting too.
—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