I do remember seeing that a long time ago, I've not encountered it with recent versions?

The thing causing this behaviour is still there, running empty loops and subtracting times.

Here's an example:

#!/usr/bin/perl use strict; use warnings; use Benchmark; timethese -1, { trivial1 => sub {1}, trivial2 => sub {2}, }; __END__ Benchmark: running trivial1, trivial2 for at least 1 CPU seconds... trivial1: 1 wallclock secs ( 1.13 usr + 0.00 sys = 1.13 CPU) @ 44 +79726.55/s (n=5062091) trivial2: 3 wallclock secs ( 1.97 usr + -0.01 sys = 1.96 CPU) @ 43 +171185.71/s (n=84615524)
BTW, it took about 5 _minutes_ to run this benchmark. And for some reason, it decided to run 'trivial2' 16 times as many times as 'trivial1'.

In reply to Re^4: &1 is no faster than %2 when checking for oddness. (Careful what you benchmark) by Anonymous Monk
in thread &1 is no faster than %2 when checking for oddness. Oh well. by diotalevi

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.