Re: Performance issue with CoreData SQLite Data Store
Re: Performance issue with CoreData SQLite Data Store
- Subject: Re: Performance issue with CoreData SQLite Data Store
- From: mmalcolm crawford <email@hidden>
- Date: Sat, 22 Oct 2005 00:34:33 -0700
On Oct 20, 2005, at 7:40 PM, mmalcolm crawford wrote:
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.
Sorry, that applies only to the XML and binary stores. The SQLite-
based store should save incrementally. What actual change are you
making? Where does Shark show all the activity is taking place?
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