That result highly surprised me, because sort is optimized for the
{$a <=> $b},
{$b <=> $a},
{$a cmp $b} and
{$b cmp $a} blocks (in the sense it recognises those blocks and does the compare internally instead of calling the block).
But then I realized that the current sort implementation is also implemented to take advantage of long runs of increasing/decreasing values - and in particulary sorted arrays.
So I decided to run the benchmark again, this time with shuffled values:
#!/usr/bin/perl
use strict;
use warnings;
use Benchmark 'cmpthese';
use List::Util 'shuffle';
our @data = shuffle 1 .. 10000;
cmpthese -1, {
'<=>' => q[@s1=sort{$b<=>$a} @data],
' - ' => q[@s2=sort{$b - $a} @data],
};
__END__
Rate - <=>
- 36.5/s -- -30%
<=> 52.3/s 43% --
That's what I'd expect.
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.