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

re: CoreData Performance Mystery


  • Subject: re: CoreData Performance Mystery
  • From: Ben Trumbull <email@hidden>
  • Date: Sun, 17 Feb 2008 17:24:38 -0800

This cuts the move time in about half.  So moving 200 books objects
now takes about 1.5 second vs. the 3 - 4 it was previously.  Using
Instruments it appears to me that this 1.5 second period is almost
entirely related to KVO stuff like didChangeValueForKey.  That seems
par for the course given that 200 relationships and inverse
relationships are changing buy I'm still somewhat surprised by how
long this takes?  So I suppose it's more of a KVO performance issue
than a CoreData one.

Mike,

Please please take a Shark sample (with embedded source, at 100us samples) and file a bug with bugreport.apple.com so we can improve things.
--


-Ben
_______________________________________________

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


  • Prev by Date: Where to enforce paragraph-cohesion policy in text system?
  • Next by Date: Re: Setting NSTextField inside drawRect:
  • Previous by thread: re: CoreData Performance Mystery
  • Next by thread: Unexpected result from -[super respondsToSelector:]
  • Index(es):
    • Date
    • Thread