• 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 performance issues
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CoreData performance issues


  • Subject: Re: CoreData performance issues
  • From: mmalcolm crawford <email@hidden>
  • Date: Tue, 21 Jun 2005 17:22:55 -0700


On Jun 21, 2005, at 5:10 PM, Tomek Piatek wrote:

For example, when ingesting a new scene we want to create a new project object only if one with the given name doesn't already exist.
We found that processing 20,000 records using this "find-or-create" approach is so slow that it makes CoreData basically useless.

This sounds "unusual". How are you determining uniqueness?
Are you doing any additional processing?
How long does it take simply to read and parse the data, without creating any managed objects?


How much memory is your application using? Is the hard drive thrashing? Is all the processing being done in a single "event loop" -- is there just one autorelease pool for the entire process...?

mmalc

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


References: 
 >CoreData performance issues (From: Tomek Piatek <email@hidden>)

  • Prev by Date: Re: Cocoa-dev Digest, Vol 2, Issue 951
  • Next by Date: Re: XCode 2.1 Debugging shows assembler by default
  • Previous by thread: CoreData performance issues
  • Next by thread: Re: CoreData performance issues
  • Index(es):
    • Date
    • Thread