comment on

-100 is too long

#!/usr/bin/perl
## spin-up hard-disk, init cache ;)
Split(); IRS_while(); IRS_map();
[download]

irate/tyerate

           Rate       IRS_map    Split      IRS_while
IRS_map    7682/s     --         0.83       0.81
Split      9284/s     1.21       --         0.97
IRS_while  9529/s     1.24       1.03       --
[download]

And from memory

my $removed = \ scalar read_file('removed.xml'); use File::Slurp;
             Rate   IRS_map IRS_while     Split
IRS_map   16544/s        --      -36%      -49%
IRS_while 25775/s       56%        --      -21%
Split     32686/s       98%       27%        --
[download]

irate/tyerate

           Rate       IRS_map    IRS_while  Split
IRS_map    16544/s    --         0.64       0.51
IRS_while  25775/s    1.56       --         0.79
Split      32686/s    1.98       1.27       --
[download]

In reply to Re^2: Benchmark results | localizing $INPUT_RECORD_SEPARATOR vs spliting contents of file on $INPUT_RECORD_SEPARATOR by Anonymous Monk
in thread Benchmark results | localizing $INPUT_RECORD_SEPARATOR vs spliting contents of file on $INPUT_RECORD_SEPARATOR by ashish.kvarma

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.


laziness, impatience, and hubris
	PerlMonks