Aighearach and I have been sharing some interesting code.

I have been exploring the efficiency differences between a few algorithms. The benchmarking results I see are difficult to explain. (See the top of the previous thread for more background.)

I would like to ask other Monks to try this code and post the results, along with the Perl version (perl -v) and OS/hardware info.

Thank you all,

Russ

#!/usr/bin/perl -w use strict; my $now = 8; my %url = ( monday => { @{[map(($_,1), (1..1000))]} } ); use Benchmark; timethese(1000000, { Grep => q{ $now = (sort grep {$_ <= $now} keys %{$url{'monday'}})[-1]; }, Ternary => q{ $now = ($now < $_ && $_ < 8 ? $_ : $now) for keys %{$url{'monday'} +}; }, Max => q{ foreach ( keys %{$url{'monday'}} ) { $now = $_ if $_ > $now }; } });

In reply to Algorithm Efficiency vs. Specialized Hardware? by Russ

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.