• 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: Performance issue with CoreData SQLite Data Store
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Performance issue with CoreData SQLite Data Store


  • Subject: Re: Performance issue with CoreData SQLite Data Store
  • From: mmalcolm crawford <email@hidden>
  • Date: Thu, 20 Oct 2005 19:40:02 -0700


On Oct 20, 2005, at 2:45 PM, email@hidden wrote:

It's a NSPersistentDocument-based application.

The problem seems to be that hitting command-S seems to save the whole file each
time, even if there hasn't been any change (or a very minor change).
I would have expected the SQL data store to be clever and only commit changes to
the disk (so I should have nearly instant saves by changing only a few bytes).
But this isn't the case. Why?

In common with NSDocument, NSPersistentDocument writes its file to a temporary location then copies it to the final destination.


mmalc

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Performance issue with CoreData SQLite Data Store
      • From: mmalcolm crawford <email@hidden>
References: 
 >Performance issue with CoreData SQLite Data Store (From: email@hidden)

  • Prev by Date: Re: Newbies: Completed Cocoa project available for download
  • Next by Date: Re: NSBezierPath containsPoint?
  • Previous by thread: Performance issue with CoreData SQLite Data Store
  • Next by thread: Re: Performance issue with CoreData SQLite Data Store
  • Index(es):
    • Date
    • Thread