3 ms·

Cocoa without first-class autocomplete is too horrible to contemplate. Unfortunately my 2010 MBP, which ran XCode 3 quite well, doesn't seem to be up to the tas

Cocoa without first-class autocomplete is too horrible to contemplate. Unfortunately my 2010 MBP, which ran XCode 3 quite well, doesn't seem to be up to the task of running XCode 4. You know something is wrong when XCode makes Java IDEs look lean & snappy.

tilltheis 15y ago
I'm on a 2009 MBP and have no such problems. Don't know where they could originate from, though.
- msutherl 15y ago
  I'm on a 2007 MBP and have no such problems.
- cageface 15y ago
  Do you mean that you find XCode 4 responsive? Compared to XCode 3? This isn't stopping me from getting work done but it's very sluggish compared to XCode 3 or even IntelliJ. Running it as a 32-bit app seems to have helped a bit.
  - 5hoom 15y ago
    Personally had no Xcode4 performance issues on 2010 MBP. Seems quite snappy to me (not running filevault though so YMMV...)
- stevenwei 15y ago
  On my 2009 MBP I noticed a significant performance decrease going from Xcode 3 to Xcode 4. It's not unusable, but Xcode 3 was quite snappy by comparison. You can improve performance slightly in the code editor by turning off the code folding and live issues (which I didn't really care for anyway), but the integrated interface builder is horribly slower than the one in Xcode 3. Of course now I've upgraded to a 2011 Macbook Air and Xcode 4 performance is now...acceptable.
jarin 15y ago
Are you using the new disk-wide FileVault in Lion? I had to turn that off because it was making MacVim and XCode both run horribly slow (apparently they both write to disk constantly).
- cageface 15y ago
  I am using Lion's whole-disk encryption but it was also really slow in Snow Leopard for me without FileVault.
  - jarin 15y ago
    This might be a long shot, but try deleting the project.xcworkspace directory for your project. I've heard doing that can speed things up.
stephen_g 15y ago
I think there's something wrong with your system... I was running XCode 4 on a 2006 Macbook (the one with a Core Duo processor), and it worked fairly well. Not as well as my 2011 MBP but it was still usable.
- cageface 15y ago
  It's usable. It's just annoyingly slow. I'm still getting work done but it feels like swimming upstream.
- uxp 15y ago
  I too run it on a 2006 MacBookPro1,1, and while it may not be lightning fast, it certainly is not slow. I've heard reports that running in 64bit mode also adds a bit of overhead, which may be impairing his performance, and which we cannot experience because we don't have 64bit processors.
sehugg 15y ago
You really need 8 GB of RAM to make it dealable.
- sunsu 15y ago
  It runs fine on my Mac mini with 2GB of ram. I guess my projects are not very large. I only do iPhone dev on it.

tilltheis 15y ago

I'm on a 2009 MBP and have no such problems. Don't know where they could originate from, though.

msutherl 15y ago
I'm on a 2007 MBP and have no such problems.
cageface 15y ago
Do you mean that you find XCode 4 responsive? Compared to XCode 3? This isn't stopping me from getting work done but it's very sluggish compared to XCode 3 or even IntelliJ. Running it as a 32-bit app seems to have helped a bit.
- 5hoom 15y ago
  Personally had no Xcode4 performance issues on 2010 MBP. Seems quite snappy to me (not running filevault though so YMMV...)
stevenwei 15y ago
On my 2009 MBP I noticed a significant performance decrease going from Xcode 3 to Xcode 4. It's not unusable, but Xcode 3 was quite snappy by comparison. You can improve performance slightly in the code editor by turning off the code folding and live issues (which I didn't really care for anyway), but the integrated interface builder is horribly slower than the one in Xcode 3. Of course now I've upgraded to a 2011 Macbook Air and Xcode 4 performance is now...acceptable.

jarin 15y ago

Are you using the new disk-wide FileVault in Lion? I had to turn that off because it was making MacVim and XCode both run horribly slow (apparently they both write to disk constantly).

cageface 15y ago
I am using Lion's whole-disk encryption but it was also really slow in Snow Leopard for me without FileVault.
- jarin 15y ago
  This might be a long shot, but try deleting the project.xcworkspace directory for your project. I've heard doing that can speed things up.

stephen_g 15y ago

I think there's something wrong with your system... I was running XCode 4 on a 2006 Macbook (the one with a Core Duo processor), and it worked fairly well. Not as well as my 2011 MBP but it was still usable.

cageface 15y ago
It's usable. It's just annoyingly slow. I'm still getting work done but it feels like swimming upstream.
uxp 15y ago
I too run it on a 2006 MacBookPro1,1, and while it may not be lightning fast, it certainly is not slow. I've heard reports that running in 64bit mode also adds a bit of overhead, which may be impairing his performance, and which we cannot experience because we don't have 64bit processors.

sehugg 15y ago

You really need 8 GB of RAM to make it dealable.

sunsu 15y ago
It runs fine on my Mac mini with 2GB of ram. I guess my projects are not very large. I only do iPhone dev on it.