I tend to write my uses of Benchmark.pm like:

use Benchmark 'cmpthese'; # ... cmpthese( -3, { aSimple => \&Simple, bSimple => \&Simple, aShort => \&Short, bShort => \&Short, aSweet => \&Sweet, bSweet => \&Sweet, } );

which prevents a performance bias based on execution order from going unnoticed. It also prevents me from getting excited about a 10% difference between Simple and Sweet when there is an 8% difference between aSweet and bSweet (which are the same code).

I recall seeing that some platforms give the performance boost to the first item run while others give the boost to the last item run, though that recollection is from so long ago that I wouldn't put much stock in it; just something to look for...

- tye        


In reply to Re: Benchmark.pm: Does subroutine testing order bias results? (twice is nice) by tye
in thread Benchmark.pm: Does subroutine testing order bias results? by jkeenan1

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.