Re: CoreData model optimization? (slow on insert with fetches)
Re: CoreData model optimization? (slow on insert with fetches)
- Subject: Re: CoreData model optimization? (slow on insert with fetches)
- From: Andrew Farmer <email@hidden>
- Date: Tue, 2 Oct 2007 13:24:42 -0700
On 02 Oct 07, at 07:47, Hell's KItchen wrote:
<snip>
Any tips to optimize the model or any suggestions. I think I'm wrong
because Mail uses CoreData and it's seems to be good as speed.
Correction: Mail does not use CoreData - at least, not in any
traditional fashion. It does use an SQLite database ("Envelope
Index"), but it only appears to be used as a cache. Deleting the
database doesn't cause any data to be lost.
Regarding your database design: I'm unsure of the purpose of the
"author" and "subject" entities. The storage overhead of storing this
data redundantly isn't likely to be all that high, and the processing
overhead of looking up the correct entities on insertion is
significant. You're probably better off just storing this data within
the parent entity and living with the fact that there's some
duplication.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden