Dear Monks i need your help again.

I have some code (not my) that use g and o matching modifiers. I think there is no need in them but this code show strange result. It ran faster than without this modifiers.

Can you explain why?

Here is code:

#!/usr/bin/perl -W use warnings; use strict; use Benchmark; my $phrase1 = 'network'; my $phrase2 = 'networK'; my ($t1, $t2); ########################################## $t1 = new Benchmark; for (1..10000000) { if ($phrase1 =~ /^network$/go) {} } $t2 = new Benchmark; print timestr (timediff ($t2, $t1)), "\n"; ########################################## $t1 = new Benchmark; for (1..10000000) { if ($phrase2 =~ /^networK$/) {} } $t2 = new Benchmark; print timestr (timediff ($t2, $t1)), "\n";

And here is result:

7 wallclock secs ( 6.40 usr + 0.01 sys = 6.41 CPU) 9 wallclock secs ( 9.06 usr + 0.00 sys = 9.06 CPU)

In reply to Why this code run faster? by Gangabass

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.