• 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: XCode editor intolerably slow
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: XCode editor intolerably slow


  • Subject: Re: XCode editor intolerably slow
  • From: Scott Tooker <email@hidden>
  • Date: Fri, 29 Jul 2005 16:42:31 -0700

I find it somewhat amusing that people assume we always develop on the latest and greatest hardware :)

I actually have a dual 2GHz processor G5 and a 17" 1Ghz Powerbook (each with 1MB memory ) that I use for work at Apple, and many others on the team and internal to Apple program on portables. In fact, sometimes I spend much more time developing/coding on the Powerbook than the (much faster) G5.

Contrary to how it may appear at times, we really do want to fix performance issues (and we have made improvements in various areas of Xcode, like file editing and the build system). However there are some areas that still need work (cough...file editing...cough).

Scott

On Jul 29, 2005, at 12:40 PM, Mason Mark wrote:

Well, I haven't had so many occurrences of thinking "yeah! and yeah that too!" while reading a single thread for quite a while.

I too think that the Xcode team would do well to run for a week or two on a a slower machine (such as, oh, say, Apple's current top-of- the-line PowerBook G4).

I am personally uninterested in making it snappy on old G4s (I'd rather the effort go to bug-fixing). However, recently I have been traveling extensively, and so I am forced to work not on my big (and beloved) dual G5 with several gigs of RAM, but on a PowerBook. (On my G5, I should add, almost none of the problems described here occur.)

But lately, I see just about all of the problems outlined in this thread. While my first recommendation is of course for Apple to increase the priority of performance, my two interim notes are:

a) Get 2GB of RAM (the max in a PowerBook). It is a *must* for working with medium+ sized projects (100-200K lines and above). My PowerBook's lower ram slot just failed (known issue) and until I get it fixed, I have only a gig--and I can literally walk to the cafe, buy coffee, and come back before GDB has launched my app in the debugger. The difference between 1GB and 2GB, I have accidentally found, is huge.

b) Hey, turning off that status bar really does speed it up--thanks for the tip, Scott! (I like the status bar, but not that much).

Based on using Xcode on a G5, it seems clear to me that these problems can and will be solved by faster hardware (duh). But until that happens, a lot of developers need to use laptops, at least sometimes. And even on the fastest laptop Apple sells, maxed out with RAM, Xcode is still a lot more tortoise than hare...

--
Mason Mark
(not, of course, speaking for) Five Speed Software, Inc. (in this instance)



On Jul 28, 2005, at 12:57 AM, Kent Sorensen wrote:


While I'm sure this subject has been discussed before I am now so annoyed at XCode that I have to vent a bit.

I've converted my fairly large project from CW recently and I'm not pleased at all. I have seen more spinning beachballs these past weeks than I have ever seen before. Clicking on a search result - beachball, clicking on a breakpoint to turn it off - usually beachball and I could go on and on.

The dog-slowness of the editor is severely interfering with productivity. I have of course already turned off every feature that might otherwise have made the XCode editor marginally cool, like indexing, code completion etc.

Many of my files are large at 3-5K+ lines and there are many of them. Chopping them up is not an option I want to pursue.

My machine is a PBG4/667MHZ 512MB and a fast internal harddisk. Not top of the line by far, but under CodeWarrior every editor operation is _instantaneous_ on that machine. It has always been a pleasure to take the machine to a coffee shop and work remotely for a few hours. That is no longer the case.

I would like to petition the XCode managers to deliberately _deny_ their developers faster machines than say a Mac mini. Tell them not to come back before XCode runs well on that machine. I find the current state of XCode pathetic.

I can live with the abysmal compile speed but for heavens sake concentrate on the editor for next version.

Kent Sorensen

_______________________________________________
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


_______________________________________________ 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
  • Follow-Ups:
    • Re: XCode editor intolerably slow
      • From: Rosyna <email@hidden>
References: 
 >XCode editor intolerably slow (From: Kent Sorensen <email@hidden>)
 >Re: XCode editor intolerably slow (From: Mason Mark <email@hidden>)

  • Prev by Date: Re: Debugger Arrow off by a few lines
  • Next by Date: Re: Debugger Arrow off by a few lines
  • Previous by thread: Re: XCode editor intolerably slow
  • Next by thread: Re: XCode editor intolerably slow
  • Index(es):
    • Date
    • Thread