A conceptual question:
Core data for the iPhone app has serial data through SQLite . I want to calculate and execute based on the properties of each object in the entire hierarchical system of objects. Calculations of both drawing and actions use the same exact properties quite simple. However, I hope both drawings and calculations on the main thread will cause some problems with UI responsiveness. Using two MOCs to access the same data, but on the different threads I feel like a little stupid for the first time (a bit, once in each thread, tree trees). Honestly, I do not believe that multi-threading will be of great help.
Will someone give general options to achieve proper app performance in this specific case?
Thank you.
First and foremost, do not be the design decisions of this, without actual performance data like this. You need to profile both a single and multi-threaded approach. She said, the best practices for multi-threading with core data direct a NSManagedObjectContext per-thread but a single NSPersistentStoreCoordinator . Since the row-level caching is done in the continuous store coordinator, it is possible that many of your traversals do not take an inappropriate uppercase.
Comments
Post a Comment