• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: CoreData huge memory usage - is this right ?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CoreData huge memory usage - is this right ?


  • Subject: Re: CoreData huge memory usage - is this right ?
  • From: Hal Mueller <email@hidden>
  • Date: Wed, 19 Dec 2007 01:29:26 -0800


On Dec 18, 2007, at 5:46 PM, Ben Trumbull wrote:

Martin,

We recommend an import use its own MOC, and simply set the undo manager on the MOC to nil. Easier, better, less filling.

MOC are not particularly expensive to create, so if you cache your PSC, you can use different MOCs for different working sets or distinct operations.

Just to be very clear, Ben: I read this to mean that it's fine to have multiple MOC's in one thread for a given PSC. Right? MOCs should not be shared across multiple threads (per documentation), but I gather that the converse is false.


Hal

_______________________________________________

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


References: 
 >Re: CoreData huge memory usage - is this right ? (From: Ben Trumbull <email@hidden>)

  • Prev by Date: Re: Creating Gray Scale Image give big leak...
  • Next by Date: Re: CoreData huge memory usage - is this right ?
  • Previous by thread: Re: CoreData huge memory usage - is this right ?
  • Next by thread: Re: CoreData huge memory usage - is this right ?
  • Index(es):
    • Date
    • Thread