The benchmark result is confirmed for better performance of
substr in the test above.
I've put
$count = 100 and reduced the input file size. Now I don't get any warning, the improvement with method Three is evaluated to be about 25%:
Benchmark: timing 100 iterations of Method One, Method Three, Method T
+wo...
Method One: 7 wallclock secs ( 7.60 usr + 0.11 sys = 7.71 CPU)
Method Two: 8 wallclock secs ( 7.83 usr + 0.11 sys = 7.94 CPU)
Method Three: 6 wallclock secs ( 5.82 usr + 0.10 sys = 5.92 CPU)
About the benchmark... I felt more confortable with about 40 CPU seconds, even if there was a warning. With repeated iterations I think some time is taken by the call, while one call with a big file is better focussing on the array extraction. But it is just my feeling... :) I'd better study the Benchmark routines to evaluate this
ciao
Roberto
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.