Re: Garbage collection, core data, and tight loops
Re: Garbage collection, core data, and tight loops
- Subject: Re: Garbage collection, core data, and tight loops
- From: Bill Bumgarner <email@hidden>
- Date: Wed, 31 Oct 2007 08:31:41 -0700
On Oct 31, 2007, at 5:37 AM, John R. Timmer wrote:
I have been periodically saving changes in the loop.
Are you asking Core Data to purge objects?
I neglected to manually purge the objects - i assume that would
involve using the ManagedObjectContext's -reset method?
Does your object graph allow partial subgraphs to exist in memory
without eventually faulting everything into memory?
At this point, I'm only importing a single type of managed object to
see how well things work with millions of records, and to make sure
the project's feasible as designed before going further, so this is
a non-issue.
... do you have any kind of caches or hashes that are effectively
keeping the objects around?
No, nothing should be retaining the objects - i'm setting values and
moving on.
I'll give it another shot with resetting the ManagedObjectContext
and see if that does the trick.
Ben will hopefully pipe up w/some info on how to do that.
I would also suggest that you move to a SAX parser, regardless, if you
haven't already done so. It'll be much faster and memory efficient
than DOM.
b.bum
_______________________________________________
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