Am 19.08.2009 um 19:18 schrieb I. Savant:
Hmm ... time to hit the books if you haven't already:
http://developer.apple.com/documentation/Cocoa/Conceptual/CoreData/Articles/cdPerformance.html#/
/apple_ref/doc/uid/TP40003468
Have you tried anything suggested there?
Fetch Limits: Not tried
The App basically loads objects and displays them in a table, so I
can't fetch only half of them as sorting depends on the contents of
the objects. I do fetches with sort descriptors though, to keep
sorting time down (always below 0.1 sec).
Batch faulting: tried
It helps but it is still too slow.
Pre-fetching: not tried
But if I understand the document right it's just a special case of
Batch Faulting and I don't see any faults fired since I use Batch
Faulting anyway
Reducing Memory Overhead: most don't apply (Garbage Collection / no
temporary managed objects)
I set the undo manager to nil
Large Data Objects (BLOBs): not used
I'd say all object are under 1k
Would switching to a different store type (other than SQL) help? The
database is not that large (in my example 55MB) maybe an atomic store
has its advantages there?
Ruotger
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com