Multiple persistent store coordinators gotchas?
Multiple persistent store coordinators gotchas?
- Subject: Multiple persistent store coordinators gotchas?
- From: Dave Dribin <email@hidden>
- Date: Wed, 15 Oct 2008 16:00:19 -0500
Hello,
I'm working on a Core Data application that does lots of processing of
the data in background threads to generate reports. I'd like to
investigate using multiple persistent store coordinators to reduce
lock contention, i.e. pattern #2, as described in the multi-threaded
chapter of the Core Data guide.
I'm thinking it is a good fit in this case as the background threads
are doing mainly read-only operations on the data. It does modify
transient properties, but I think I can still get away with using a
read-only store on the background threads. Is this correct?
The documentation is a little thin about using multiple PSCs. Is it
just a matter of setting up separate Core Data stacks per thread?
What are the downsides, especially compared to 1 PSC/multiple MOCs?
Higher memory usage? Separate caches? Stale data? Anything else to
watch out for?
Thanks,
-Dave
_______________________________________________
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