I know Perl maintains a pointer (offset), within an SV, of where actual data in PV buffer starts, -- is this "beheading" the reason for the slowdown as demonstrated?

use strict;
use warnings;
use Benchmark 'cmpthese';

my $str = ' ' x 1e5;

sub test1 {
    my $s = shift;
    my $copy = substr $str, 1;
    1 while $copy =~ /./g;
    _:
}

sub test2 {
    my $s = shift;
    substr $s, 0, 1, '';
    1 while $s =~ /./g;
    _:
}

cmpthese -1, {
    test1 => sub { test1( $str )},
    test2 => sub { test2( $str )},
};

#             (warning: too few iterations for a reliable count)
#         Rate test2 test1
# test2 2.79/s    --  -93%
# test1 41.0/s 1372%    --

[download]

In reply to Are beheaded strings known to be slow? by Anonymous Monk

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.