Why speculate?
#!/usr/local/bin/perl -w use Benchmark; $count = 1_000_000; print "Match eq => ", check_eq(), "\n"; print "Match rx => ", check_rx(), "\n"; timethese( $count, { 'eq' => sub{ check_eq() }, 'rx' => sub{ check_rx() } } ); sub check_eq { my $thing = "thing"; my $i = 0; $i++ if( $thing eq "thing" ); $i; } sub check_rx { my $thing = "thing"; my $i = 0; $i++ if( $thing =~ /^thing$/ ); $i; }
reveals
Match eq => 1 Match rx => 1 Benchmark: timing 1000000 iterations of eq, rx... eq: 15 wallclock secs (14.27 usr + 0.00 sys = 14.27 CPU) @ 70 +093.46/s (n=1000000) rx: 22 wallclock secs (21.08 usr + 0.00 sys = 21.08 CPU) @ 47 +430.83/s (n=1000000)

In reply to Re: Which is better when doing a simple match? by Anonymous Monk
in thread Which is better when doing a simple match? by mr.dunstan

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.