On Aug 5, 2015, at 20:17 , Juanjo Conti <jjco...@carouselapps.com> wrote: > > At the moment I'm using Keyed-Archiving, but after detecting performance > issues and read I'm changing to Core-Data.
What quantity of entries/records are you talking about here? It’s not going to make a big difference to performance (as opposed to a smaller, custom solution that doesn’t involved archiving, if that is in fact the bottleneck) unless you have tens of thousands of records to store. IMO, Core Data is a terribly painful technology that will make you very, very miserable, not to mention adding many months to your project. As an alternative, if your use case is really a kind of database, you could try using something like sqlite or couchDB (whatever it’s called now, I’m sure Jens would be happy to fill you in). If it’s not, write a custom data file and be done with it. I don’t know for sure, but my impression is that the things that are slow in archiving are: — Following links in a non-hierarchical object graph. — Uniquing values stored as objects, such as NSString and NSNumber. _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
