Re: Hex to NSString or NSData
Re: Hex to NSString or NSData
- Subject: Re: Hex to NSString or NSData
- From: Greg Guerin <email@hidden>
- Date: Sat, 9 May 2009 19:20:20 -0700
Gwynne Raskind wrote:
Yeah, but since that was only done as part of a benchmark, it
didn't much matter. It may have skewed the numbers upwards
unnecessarily, but wouldn't have changed their relation to each
other since the same sequence was calculated for all three versions.
It changes the validity of terms like "by a factor of about two"
because you haven't accounted for the overhead costs properly. The
overall times differ by a factor of two, but the code under test may
not be faster by a factor of two.
Given the data:
t(overhead) + t(c1) = t1
t(overhead) + t(c2) = t1/2
This does not imply t(c1) equals t(c2)/2, unless t(overhead) is 0.
The % may still not matter much, but you can't infer it from the
reported data.
-- GG
_______________________________________________
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