Re: CoreData - large data set is slow to load on app launch - optimisation tips?
Re: CoreData - large data set is slow to load on app launch - optimisation tips?
- Subject: Re: CoreData - large data set is slow to load on app launch - optimisation tips?
- From: Chris Hanson <email@hidden>
- Date: Sat, 3 Dec 2005 14:43:23 -0800
On Dec 3, 2005, at 11:57 AM, Simon Liu wrote:
I wonder if the coredata folk can tell me if its a good idea to have
data blobs like images all stored in a separate data store or not?
Core Data doesn't support cross-store relationships, so you'd have to
do the relationship maintenance and management yourself if you did
this. (Transient attributes are useful for this.)
Generally, the advice in the general database community is to store
large binary data outside the database, in the filesystem, and only
store a reference to it in the database. However, everybody has a
different idea of what "large" is in such a context, and it also
means that you have to deal with the possibility that the user may
modify the filesystem underneath your app.
Generally, I'd say try keeping your binary data on the other side of
a relationship first if they're not too large (e.g. faulting in one
takes less than a second) but be prepared to switch their storage to
the filesystem if necessary. You should be able to accomplish this
with minimal disturbance to the rest of your app's code, since it'd
really only be the internals of your Image entity that change.
-- Chris
_______________________________________________
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