Added one more test case
my %tests = (
split => q{ my @a = split //, $buf; },
regex => q{ my @a = $buf =~ /./sg; },
unpack_C => q{ my @a = map chr, unpack 'C*', $buf; },
unpack_a => q{ my @a = unpack '(a)*', $buf; },
rev_chop => q{ my @a = reverse map chop($buf), 1..length($buf); },
chop => q{ my @a; $a[ $_ ] = chop $buffer for length($buffer) .. 0;
+ },
);
And result was
Rate rev_chop unpack_C split regex unpack_a chop
rev_chop 17.6/s -- -6% -13% -20% -30% -100%
unpack_C 18.7/s 6% -- -7% -15% -25% -100%
split 20.2/s 15% 8% -- -8% -20% -100%
regex 22.0/s 25% 17% 9% -- -13% -100%
unpack_a 25.1/s 43% 34% 24% 14% -- -100%
chop 68478/s 388556% 365714% 339175% 311691% 272542% --
However I am yet to read "Benchmark" so someone please explain this output. :)
UPDATE: Sorry! That was a silly mistake.
Thanks almut.
-
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.