On Wed, Jun 18, 2008 at 5:17 PM, Markus Spoettl <[EMAIL PROTECTED]> wrote: > On Jun 18, 2008, at 1:59 PM, Quincey Morris wrote: >> >> Yes, but look at where the time is *really* being spent. At a guess, >> finishEncoding is comparing every number object against every other number >> object to see if it can archive just one object of each distinct numeric >> value. With the number of objects you said you're using, this O(n**2) >> optimization -- if that's what it's doing -- is hideously expensive. > > > Exactly and the test data isn't particularly big. Any ideas how to tell the > archiver not to do this with my doubles (that doesn't involve conversion to > strings and back)?
Although it partially defeats the purpose of using NSCoder, you'll avoid this whole path if you stuff all four doubles into a single NSData. Don't forget to use the byte-swapping functions to ensure that they all have a consistent representation across architectures. Mike _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
