Re: Core Data performance (was: Newbie Help understanding Core Data)
Re: Core Data performance (was: Newbie Help understanding Core Data)
- Subject: Re: Core Data performance (was: Newbie Help understanding Core Data)
- From: Bill Bumgarner <email@hidden>
- Date: Thu, 28 Jul 2005 15:17:58 -0700
On Jul 28, 2005, at 12:55 PM, Charilaos Skiadas wrote:
So again my question, and that's really my final question on this,
has anyone (maybe Apple?) done measurements to compare a generic
Core Data app versus the corresponding app in a non-Core Data way,
and compared the runtime performance of the two?
We did exactly that throughout the development of Core Data and the
team continues to carefully monitor performance numbers throughout
development. There are certainly still opportunities for optimization.
As per storage, NSManagedObject uses an internal storage mechanism
for data that is highly optimized. In particular, it leverages the
knowledge about the types to be stored that are available via
introspecting the model. For storage and retrieval of data,
including KVO and KVC interactions, using NSManagedObject will very
likely be faster than any storage mechanism including the simple
getter/setter case.
Given that a modern Cocoa application will be implemented with heavy
use of bindings and bindings makes heavy use -- is entirely reliant
upon -- KVO and KVC, it would be very difficult to build a raw data
storage mechanism that provides the same level of efficiency as Core
Data while also driving a Cocoa Bindings heavy UI.
Now, to address the question "for simple data, what is the point of
Core Data?". Even a simple application will likely need undo, redo,
validation, relationships between objects, and the ability to save.
Core Data gives you all of that for free.
b.bum
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden