Converting Hexadecimal in Binary

[Ken Ray]

it's a bit faster... here's the "old" test:

"Original = 5.866667 seconds 
"200% Faster" = 0.25 seconds (23x Faster!)
"400% Faster" = 0.166667 seconds (35x Faster!)

and the new one:

"Original = 5.666667 seconds 
"200% Faster" = 0.233333 seconds (24x Faster!)
"400% Faster" = 0.15 seconds (38x Faster!)

Ken Ray
Sons of Thunder Software
Email: kray at sonsothunder.com
Web Site: http://www.sonsothunder.com/ 


> -----Original Message-----
> From: Dar Scott [mailto:dsc at swcp.com]
> Sent: Sunday, January 11, 2004 11:56 AM
> To: kray at sonsothunder.com; How to use Revolution
> Subject: Re: Converting Hexadecimal in Binary
> 
> 
> 
> On Saturday, January 10, 2004, at 08:46 PM, Ken Ray wrote:
> 
> >> This is 400% faster than original!!!!!!!!!!
> >
> > Actually, I got a MUCH greater time savings, Alejandro...
> 
> The problem might be that putting the data into the field is
> inside the 
> timing test.  That adds an offset to the timing.  If that is put 
> outside the timing bracket, we should see even greater 
> results.  Also, 
> we should see different results on different platforms.
> 
> How does this look with just the computation and without putting the
> value into the field?
> 
> Dar Scott
> 
> ****************************************
>      Dar Scott Consulting
>      http://www.swcp.com/dsc/
>      Programming Services
> ****************************************
> 
>