Re: creating classes on the fly ??
Re: creating classes on the fly ??
- Subject: Re: creating classes on the fly ??
- From: Daniel Child <email@hidden>
- Date: Wed, 26 Sep 2007 17:18:05 -0400
My prototype simply uses NSSet and NSDictionary, but that is so I can
work out other issues.
I'd rather avoid C++ if I can.
You seem to be recommending Core Data, though others are recommending
Python. Are they either or? I thought Python would replace Obj-C
syntax, whereas Core Data provides a chance to use data structures
Apple provides.
I've read a little about Core Data but am still not that clear on
what happens when you use it.
On Sep 22, 2007, at 11:07 AM, Thomas Engelmeier wrote:
Am 22.09.2007 um 15:52 schrieb Daniel Child:
As the lexicons and corpus data get large (say up to half a
million or even a million records), are the "standard" data
containers going to pose performance problems?
EVERY container will pose an performance problem with 1 Mega
entries and an inappropriate algorithm.
I'd recommend to write an tiny prototype that generates some
arbitrary, random dataset and profiles your typical data access
pattern (search 100 entries). Profile should include timing and
memory, as soon your app starts swapping you have an immense
performance hit.
- Cocoa data structures -> easiest to use, might be inefficient
- C++ std:: data structures -> no serialisation buildt in, beware
std::string is not Unicode-Savy
- Core Data -> Even with an far higher abstraction layer it might
be faster due to under-the-hood paging out of unused entries.
Regards,
Tom_E
_______________________________________________
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