use strict;
use warnings;
use Benchmark qw/ cmpthese /;
my $R = 'R' x 42_000;
my $Q = 'Q' x 42_000;
sub foo {
my $c = shift;
pos $$c = 0;
while ( 1 ) {
next if $$c =~ /\G\d+R/;
last unless $$c =~ /\w/g;
}
}
cmpthese -3, {
R => sub { foo( \$R )},
Q => sub { foo( \$Q )},
}
C:\>perl test.pl
Rate Q R
Q 1.30/s -- -96%
R 30.9/s 2279% --
I'd expect both strings should behave the same (match fails immediately) in line which starts with next, but it's obviously not so. There's some weird internal "optimization" going on here, but why?
And it's not just idle curiosity, dear monks. Look here. Syntax like 42 0 R is "indirect object" ("R" for "reference"), i.e. "R" is kind of "special". It so happens that huge (150 Mb) page content has no "R"'s, and it takes forever to parse this string :(.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.