• 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: Snapshots too slow to be usable?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Snapshots too slow to be usable?


  • Subject: Re: Snapshots too slow to be usable?
  • From: James Bucanek <email@hidden>
  • Date: Fri, 7 May 2010 09:09:31 -0700

Larry Campbell <mailto:email@hidden> wrote (Thursday, May 6, 2010 3:04 PM -0400):

If this is typical,

No. Basically, a snapshot makes a copy of all of your project files to a disk image in ~/Library. Unless you have some unusual number or arrangement of files, it shouldn't take more than a few seconds even for moderately sized projects.


If yours are taking a long time, you might sample Xcode to see what's its doing, and definitely file a bug report if this is reproducible.

As others have pointed out, discarding the disk image in ~/Library will discard/reset all snapshots (make sure you've quit Xcode before doing that). That alone might solve the problem. Examining the disk image might also shed some light. Maybe Xcode is copying *way* more than you expected for some reason. Regardless, file a bug report.

I can't believe anyone actually uses snapshots.

Snapshots are awesome. I use them all the time.

Snapshots are incredibly freeing, especially for experimentation and testing. Have you ever found yourself writing some code, didn't like it, commenting it out, and writing some more code, commenting that out, ad nauseam? You want to try something different, but you don't want to abandon the work you've already done?

That's what snapshots are for. If you want to try something, take a snapshot and try it. If it works, keep it. If not, throw it all away and revert back to the snapshot, or compare the two and pick and choose what you like from each, or just compare the two to see what the differences are, or take another snapshot and keep on experimenting.

In short, snapshots are lightweight mechanism for capturing your progress at strategic points in your development. They are not, however, a source control system or a replacement for backups. In fact, you should be careful not to overlap the two (i.e. take snapshot, make change, check changes into SCM, restore from snapshot).


James Bucanek ____________________________________________________________________ Author of Professional Xcode 3 ISBN: 9780470525227 <http://www.proxcode3.com/> and Learn Objective-C for Java Developers ISBN: 9781430223696 <http://objectivec4java.com/>

_______________________________________________
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: Snapshots too slow to be usable?
      • From: Joar Wingfors <email@hidden>
References: 
 >Snapshots too slow to be usable? (From: Larry Campbell <email@hidden>)

  • Prev by Date: DTrace: Probe Performance Hit
  • Next by Date: Re: ibtool --convert
  • Previous by thread: Re: Snapshots too slow to be usable?
  • Next by thread: Re: Snapshots too slow to be usable?
  • Index(es):
    • Date
    • Thread