This looks really weird (excuse the hacked OO - for demo purposes only :)

#!/usr/bin/perl use strict; use warnings; use Benchmark 'cmpthese'; my $self = bless [123], '::main'; cmpthese( 10000000, { normal => $self->a(), optimized => $self->b(), direct => $self->c(), }); exit(0); sub a { # old school accessor $self->get_value(); } sub b { # optimized accessor $self->get_value2(); } sub c { # fast and nasty, non oo accessor $self->[0]; } sub get_value { my $self = shift; return $self->[0]; } sub get_value2 { $_[0]->[0]; }

You would expect the direct method to benchmark fastest, but I got this:

Rate optimized direct normal optimized 12549020/s -- -1% -1% direct 12673267/s 1% -- 0% normal 12673267/s 1% 0% --

Am I missing something, or is that just plain weird?


In reply to Unexpected OO accessor benchmarks by cLive ;-)

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.