Hmm. And just when I thought it was safe to go back into the water, I added one more thing into the mix. Both subroutines contain:
while ( <FH> ) {
.. and below each such line, I added:
next if $_ !~ /mapi/io;
("MAPI" is the string being tested for.)
It's the crudest possible test, of course. But why bother with further processing if the string doesn't appear anywhere in the current line?
With that statement added, there was a considerable difference in the benchmarked results:
Benchmark: timing 30 iterations of REGEXP, SPLIT...
REGEXP: 14 wallclock secs (14.35 usr + 0.19 sys = 14.54 CPU)
SPLIT: 17 wallclock secs (16.01 usr + 0.28 sys = 16.29 CPU)
I should have read my own pep-talk about trying stuff...
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
