• 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: I'm killing my database
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: I'm killing my database


  • Subject: Re: I'm killing my database
  • From: Guido Neitzer <email@hidden>
  • Date: Tue, 24 Apr 2007 23:32:10 -0600

On 24.04.2007, at 20:59, Chuck Hill wrote:

The first thing I would do is to add this line:
recordContext .undoManager().removeAllActions();

The next thing I would do (voodoo or not) is to periodically dispose of recordContext and create a replacement. In the past that was vital.

It still is. It helps. Not necessarily for performance but normally for memory usage. I normally do bulk import in batches of up to 500 objects per batch, then save and dispose the editingContext, set it to null and create in new one in the next batch. Also for bulk updating of EOs.


That works well for my importers.

If you need to resolve relationships during import, pre-fetching the relationships can make a huge difference.

cug
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: I'm killing my database
      • From: Chuck Hill <email@hidden>
References: 
 >I'm killing my database (From: Scott Winn <email@hidden>)
 >Re: I'm killing my database (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: java.lang.NoClassDeffoundError: Application
  • Next by Date: Re: Fetch canceled
  • Previous by thread: Re: java.lang.NoClassDeffoundError: Application
  • Next by thread: Re: I'm killing my database
  • Index(es):
    • Date
    • Thread