You use 'benchmark' in your testing environment to see which sequence of Perl declarations and statements produce the *best* result. You determine the meaning of *best*, but if the results are almost, you're missing the value of 'benchmark'.
For example, you may be testing the use of an array or a hash within different subroutines, but the final result ( whatever you determine is the result ) must be the same. You may determine that the subroutines produce a file, and that file must be the exact same for all the different subroutines you 'benchmark'.
Humans ( including programmers ) don't have the exactness of computers and that's why we need a great script like 'benchmark' to run our different scripts hundreds/thousands/millions of times to give us the best sequence.
Almost isn't the same as equal!
Regards...Ed
"Well done is better than well said." - Benjamin Franklin
In reply to Re^6: Inconsistent Results with Benchmark
by flexvault
in thread Inconsistent Results with Benchmark
by benwills
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |