The for and map implementations have to recompile the regex on each iteration, but the alternation doesn't have that limitation. Here's a modified version that fixes that:

use strict;
use warnings;
use Benchmark 'cmpthese';
undef $/;
my $str = <DATA>;

my @regexen = ( qr/foo/, qr/bar/ );
cmpthese(-2, {
        alternation => sub { my @m = $str =~ /(foo|bar)/g },
        map         => sub { my @m = map $str =~ /$_/g, @regexen },
        loop        => sub { my @m; push @m, $str =~ /$_/g for @regexe
+n },
});

cmpthese(-2, {
        alt_s  => sub { my $s2 = $str; $s2 =~ s/(foo|bar)//g },
        loop_s => sub { my $s2 = $str; $s2 =~ s/$_//g for @regexen}
});

__DATA__
This string contains foo and bar for fools and bards
and I pity the foo who bars the way

[download]

I got results more consistant with the OP:

               Rate alternation         map        loop
alternation 26962/s          --        -61%        -64%
map         68918/s        156%          --         -9%
loop        75551/s        180%         10%          --
          Rate  alt_s loop_s
alt_s  32434/s     --   -20%
loop_s 40707/s    26%     --

[download]

Just for kicks, I added a study $str; right after reading the DATA filehandle. I know study is rarely useful, but it's supposed to help in situations where a single string is going to be matched against many different regexen, which is roughly what we have here. Results:

               Rate alternation        loop         map
alternation 26569/s          --        -56%        -60%
loop        60015/s        126%          --        -10%
map         66863/s        152%         11%          --
          Rate  alt_s loop_s
alt_s  31355/s     --   -19%
loop_s 38857/s    24%     --

[download]

The speed drops across the board, but alternation is only affected by 1.5% (which is insignificant noise). But loop gets hit hard.

"There is no shame in being self-taught, only in not trying to learn in the first place." -- Atrus, Myst: The Book of D'ni.

In reply to Re^2: Regex combining /(foo|bar)/ slower than using foreach (/foo/,/bar/) ??? by hardburn
in thread Regex combining /(foo|bar)/ slower than using foreach (/foo/,/bar/) ???   by JollyJinx

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.