|
You should also time them for Multiplication, division and addition. Just moving memory around doesn't take up that much CPU time. Doing math on numbers is the CPU cruncher. Regards, Jim Langston -----Original Message----- From: Scott Klement [mailto:klemscot@klements.com] (Reply snipped here and there to appease bandwidth daemons) Hey... you forgot floating point... :) On Wed, 6 Feb 2002, Buck Calabro wrote: > > To test my assumptions, I ran some loops with no optimisation. 50k > iterations, 500k and 5 million. Times are in seconds. > sample code: > > d LIMIT c const(5000000) > d start s t > d stop s t > d diff s 10i 0 > > d numZ10 s 10s 0 > d numP10 s 10p 0 > d numI10 s 10i 0 > d numB09 s 9b 0 > d numZ09 s 9s 0 > d numP09 s 9p 0 > > c eval numZ10 = LIMIT > c time start > c do numZ10 > c enddo > c time stop > c stop subdur start diff:*s > c diff dsply > > One loop for each "num" D-spec above... > --buck
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.