Re: CoreData/NSManagedObject accessor performance problems
Re: CoreData/NSManagedObject accessor performance problems
- Subject: Re: CoreData/NSManagedObject accessor performance problems
- From: Andrew Bush <email@hidden>
- Date: Mon, 18 Dec 2006 12:17:28 +1300
Hi all,
ok, so I got the filterPredicate working. yay :) unfortunately it
appears t be about comparable with the other filtering methods in terms
of speed...presumably it is doing much the same thing.
so, I guess Im looking at having to create an NSData that holds a bunch
of field values just for the purpose of having to only unwrap it
once.....unless...
it appears that sqlite is only storing the data values, so one of the
things that is happening here is for every comparison I am creating a
NSNumber out of a double (stored in sqlite), and then comparing its
doubleValue with the double I am filtering it on.
and the creation of the NSNumber is apparently where the speed hit is
coming from....it goes from being pretty much instant to do a straight
iteration of the 3000 objects using NSEnumerator in arrangeObjects to
taking around 6 seconds if I simply access a single value on each
object.
so..is there some (any) way for me to just get at the raw value without
bothering with the NSNumber stuff? presumably NSManagedObject stores
that somewhere......how can I access it directly?
thanks again for any help....if I can just get this sorted Im looking
pretty good )
Yours cheerfully,
Andrew Bush
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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