D'oh! I optimized the split but not the regex :( That'll teach me to be careless. For honesty's sake:
timethese(1000000, {
Regex => '$a=$1 if $myvar =~ /^[^,]+,([^,]+)/',
Split1 => '$result = (split /,/, $myvar)[1]',
Split2 => '$result = (split /,/, $myvar, 4)[1]',
Split3 => '$result = (split /,/, $myvar, 3)[1]'
});
Benchmark: timing 1000000 iterations of Regex, Split1, Split2, Split3.
+..
Regex: 14 wallclock secs (14.12 usr + 0.00 sys = 14.12 CPU)
Split1: 17 wallclock secs (16.54 usr + 0.00 sys = 16.54 CPU)
Split2: 16 wallclock secs (16.75 usr + 0.00 sys = 16.75 CPU)
Split3: 14 wallclock secs (13.02 usr + 0.00 sys = 13.02 CPU)
I'm going to cry myself to sleep tonight.
Curiously, though, it was the null assignments that appeared to be killing the efficiency ($a=$1, $b=$2, $c=$3, $d=$4) much more than the unoptimized regex. Hmmm....
Cheers,
Ovid
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.