Re: Core Data memory not freed after reset
Re: Core Data memory not freed after reset
- Subject: Re: Core Data memory not freed after reset
- From: "Sean McBride" <email@hidden>
- Date: Tue, 22 Sep 2009 17:05:31 -0400
- Organization: Rogue Research Inc.
On 9/22/09 1:59 PM, Ben Trumbull said:
>>> If you're using an NSArrayController in Entity mode, you can turn on
>>> Use Lazy Fetching. You'll want to disable auto-rearrange content.
>>
>> Ben,
>>
>> May I ask, why turn off 'auto-rearrange content'? Is it not
>> compatible
>> with 'use lazy fetching'? Or does
>> 'auto-rearrange content' on its own degrade performance somehow?
>
>
>auto-rearrange content is very expensive. Preserve selection can also
>be expensive, although not nearly as bad. But if we're talking about
>a million object table view (which is a little odd, btw, most UIs have
>"... and more" instead) then extraneous layout options will add up fast.
Thanks for this info.
>I have a vague and hazy memory that auto-rearrange content is not
>compatible with use lazy fetching. If you run into trouble, file a
>bug, and disable auto-rearrange content as a workaround.
I asked because I've just recently turned 'auto-rearrange content' ON in
most of my array controllers (so that my tableviews stay sorted when the
user changes some string). My tables rarely have more that 10 rows
though. I've not yet tried lazy fetching but am now forewarned. :)
Thanks,
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
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