Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
in my app i need to save some data. Right now i use CoreData, i have an entity with 6 attributes. In my database there are around 40 objects of this entity.
So my question is, if it is better to save them in a plist? I don’t have experience with performance of these two techniques but i think plist’s are for smaller list of objects but it’s faster and for CoreData it’s the opposite.
What would u say?
Actually, for large data stores, Core Data will be faster. Plists can’t be loaded partially, so if you want to load anything at all you need to read in the entire store, and that means time wasted as well as unnecessarily high memory usage. Core Data, on the other hand, knows how to retrieve only the resources you need, when you need them.
In your case, just go with Core Data. The learning curve is steeper, but it’s worth it.