I wrote this simple script just because I thought that 'grep' would be faster than 'for' and was justified replace appropriate 'for' loops. 
#!/usr/bin/perl
use strict;
use warnings;

my @values = qw(test test1 test2 test3);

use Benchmark qw( cmpthese );

cmpthese -2, {
    for_loop  => sub { my @matches; for (@values) { push @matches, $_ 
+if $_ =~ qr{test} }; },
    grep_loop => sub { my @matches = grep { $_ =~ qr{test} } @values; 
+                     },
};
__END__
             Rate grep_loop  for_loop
grep_loop 66674/s        --      -10%
for_loop  74136/s       11%        --

This is perl, v5.8.8 built for i486-linux-gnu-thread-multi

[download]

I was a little suprised by this and I was wondering if maybe there was something else I was missing. Any comments?

In reply to Battle Royal Grep vs For by Herkum

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.