cunning indeed, significantly faster.

Benchmark: running for_loop, map_void, new_guy, nonvoid_1, nonvoid_2 f +or at least 3 CPU seconds... for_loop: 4 wallclock secs ( 3.19 usr + 0.00 sys = 3.19 CPU) @ 15 +55.17/s (n=4961) map_void: 3 wallclock secs ( 3.29 usr + 0.00 sys = 3.29 CPU) @ 11 +30.40/s (n=3719) new_guy: 3 wallclock secs ( 3.07 usr + 0.00 sys = 3.07 CPU) @ 19 +67.10/s (n=6039) nonvoid_1: 3 wallclock secs ( 3.15 usr + 0.00 sys = 3.15 CPU) @ 33 +9.37/s (n=1069) nonvoid_2: 3 wallclock secs ( 3.15 usr + 0.01 sys = 3.16 CPU) @ 13 +9.87/s (n=442)

Cheers,
R.

Pereant, qui ante nos nostra dixerunt!

In reply to Re^5: Counting unique elements in an array by Random_Walk
in thread Counting unique elements in an array by Anonymous Monk

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.