Hmm. I disbelieve that using alternation is as efficient as looping over a list of patterns. I believe the following benchmark backs me up: 

tilly gives: 1600
chetlin gives: 1600
Benchmark: running chetlin, tilly, each for at least 5 CPU seconds...
   chetlin:  9 wallclock secs ( 5.52 usr +  0.00 sys =  5.52 CPU) @ 33
+3.70/s (n=1842)
     tilly: 10 wallclock secs ( 5.09 usr +  0.00 sys =  5.09 CPU) @ 10
+4.52/s (n=532)

[download]

Here's the code for it; do feel free to slap me around if I made a thinko: 

my @patterns=qw/foo bar baz blarch/;
my $tilly=qr/(@{[join "|",@patterns]})/;
my @chetlin=map qr/$_/,@patterns;
my $target="foo baz blarcy foo blarch"x400;

sub tilly {
    my $count;
    $count++ while ($target =~ /$tilly/g);
    print STDERR "tilly gives: $count\n" if ((caller)[1]!~/eval/);
}

sub chetlin {
    my $count;
    for (@chetlin) {$count++ while ($target =~ /$_/g) }
    print STDERR "chetlin gives: $count\n" if ((caller)[1]!~/eval/);
}

tilly();
chetlin();

use Benchmark;

timethese(-5, { tilly   => \&tilly,
                chetlin => \&chetlin,
});

[download]

In general, my credo is to avoid alternation at all costs. I would be interested in seeing what a benchmark of your optimized alternation (ref. the pointer you gave above) would give.

-dlc

In reply to RE: RE (tilly) 2: efficiency & style by dchetlin
in thread efficiency & style by djw

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.