• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: G4 867mhz, Leopard, and XCode 3
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: G4 867mhz, Leopard, and XCode 3


  • Subject: Re: G4 867mhz, Leopard, and XCode 3
  • From: Doug Hill <email@hidden>
  • Date: Wed, 16 Apr 2008 19:05:00 -0700

On Apr 16, 2008, at 6:38 PM, Steve Checkoway wrote:

On Apr 16, 2008, at 2:33 PM, Jeremy Pereira wrote:

I'm running a first gen MacBook Pro on an upgrade install of Leopard and Xcode 3 runs just fine. I do have 2Gb RAM so I guess the answer is stuff your machine with as much RAM as possible, but then that's always the answer.


That's not a reasonable answer. A glorified text editor should not require a gigabyte of ram. As computers have gotten faster, computer programs have required more ram and faster processors. The source code is no more difficult to edit than it was a decade ago. Writing text should be a solved problem.

Just wanted to reiterate since people keep giving these sweeping generalizations about Xcode memory requirements...


The editor part of Xcode 2.x ran quite acceptably on my 450Mhz G4 tower with 1GB of RAM. Not extra-snappy but well enough to be quite productive. What really kills performance is a RAM starved machine when doing builds. The GCC tools, particularly the compiler are massive memory hogs and will eat up 2GB of RAM doing slightly non- trivial compiles. They could take up more depending on what you are building. If you don't have at least that much RAM, the OS will page to disk which will kill your performance by at least 100x. Xcode the application can't do much about that since it's just launching processes for the various GCC tools. So, the RAM is going towards builds not the Xcode application itself. Check System Profiler and see where your performance problems are. See which processes are using how much CPU cycles and RAM and if they causing paging to disk.

While we could complain about GCC being a pig, I don't think it's that wrong to expect a developer to have an extra $50 worth of RAM in a machine that costs $1000-$2000.

Doug Hill
_______________________________________________
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


References: 
 >G4 867mhz, Leopard, and XCode 3 (From: P Teeson <email@hidden>)
 >Re: G4 867mhz, Leopard, and XCode 3 (From: Thomas Engelmeier <email@hidden>)
 >Re: G4 867mhz, Leopard, and XCode 3 (From: William Bates <email@hidden>)
 >Re: G4 867mhz, Leopard, and XCode 3 (From: "Wesley Smith" <email@hidden>)
 >Re: G4 867mhz, Leopard, and XCode 3 (From: "Adam R. Maxwell" <email@hidden>)
 >Re: G4 867mhz, Leopard, and XCode 3 (From: Joachim Deelen <email@hidden>)
 >Re: G4 867mhz, Leopard, and XCode 3 (From: Jeremy Pereira <email@hidden>)
 >Re: G4 867mhz, Leopard, and XCode 3 (From: Steve Checkoway <email@hidden>)

  • Prev by Date: Re: G4 867mhz, Leopard, and XCode 3
  • Next by Date: Re: G4 867mhz, Leopard, and XCode 3
  • Previous by thread: Re: G4 867mhz, Leopard, and XCode 3
  • Next by thread: Re: G4 867mhz, Leopard, and XCode 3
  • Index(es):
    • Date
    • Thread