On Jul 26, 2009, at 5:52 PM, Adam R. Maxwell wrote:
"CFString objects perform other “tricks” to conserve memory, such as
incrementing the reference count when a CFString is copied."
http://developer.apple.com/documentation/CoreFoundation/Conceptual/CFStrings/Articles/StringStorage.html#//apple_ref/doc/uid/20001179
Exactly what I was looking for, thanks. I stand corrected and give
Aaron back the "probably right" upgraded to a full "you're absolutely
right". :-)
"Reasonably large files" is reasonably vague :).
Quite. Back to the old "we don't know the OP's requirements".
Because of this, vague (and covering as many caveats as possible) is
the best answer.
We have an application that keeps an array of bibliographic
references, where each is an NSMutableDictionary with other
properties. The largest file I recall throwing at it is ~20K items,
and the main problem at that point was a beachball when using
SearchKit...which was a nuisance to work around. It doesn't use
bindings, but there really aren't any lazy loading tricks either.
Well ... 20k items with only a couple of columns or 20k items with
"many" columns. That one little detail makes all the difference. :-)
--
I.S.
_______________________________________________
Cocoa-dev mailing list ([email protected])
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
