I guess the necessity to scan and page in memory is a legitimate downside for
VM systems. It's possible I've seen xcode pause when switching apps, but never
thought about it being related to GC scans, but just paging in the app. I'd
probably forgotten that XCode is GC.
...of course, the iPhone does not have virtual memory, so its not an issue
there.
________________________________
From: Adam R. Maxwell <amaxw...@mac.com>
To: cocoa-dev Dev <cocoa-dev@lists.apple.com>
Sent: Friday, 26 June, 2009 1:32:51 PM
Subject: Re: GC pros and cons
On Jun 25, 2009, at 8:19 PM, Chris Idou wrote:
> I still use XCode in one location where I work on a core-solo Mini.
> Performance is good. No problems at all, no pauses.
Interesting. I found the Xcode editor to be unusably slow on a PowerBook G4
when Leopard was released; in fact, contrary to Bill's statement, I found that
it grew worse in the last few months of Leopard seeding. I'm still sore about
having to buy a MacBook Pro just to avoid beachballs while typing
(rdar://problem/5572897). Even said MacBook Pro needs 4 GB of RAM to avoid
hanging when switching to Xcode, since the collector thread evidently causes
paging in to scan memory (which caused a beachball and hiccups switching apps
in Spaces).
Access Yahoo!7 Mail on your mobile. Anytime. Anywhere.
Show me how: http://au.mobile.yahoo.com/mail
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
