As Corion pointed out, the switch from !$_ to /0/ is overpowering the other differences and invalidating your test.

But other improvements can be made.


There's no reason to use an intermediate array in the latter snippet. This avoids the creation of 5 million scalars.

my @e = grep !$_, map $_ % 2, @c;

You could even eliminate the grep.

my @e = map $_ % 2 ? () : 0, @c;

Similar improvements can be made for the foreach version.

my @e; for my $c ( @c ) { my $d = $c % 2; push @e, $d if !$d; }
my @e; for my $c ( @c ) { push @e, 0 if !( $c % 2 ); }

Finally, I'm curious how these compare:

my @e = ( 0 ) x grep !( $_ % 2 ), @c;
my @e; push @e, 0 for 1 .. grep !( $_ % 2 ), @c;

In reply to Re: Speed comparison of foreach vs grep + map by ikegami
in thread Speed comparison of foreach vs grep + map by mldvx4

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.