Benchmark: timing 100000 iterations of Reference Implementation, Rever +se Array, Shorter Array, strftime... Reference Implementation: 1 wallclock secs ( 0.66 usr + 0.03 sys = +0.69 CPU) @ 144927.54/s (n=100000) Reverse Array: 1 wallclock secs ( 0.85 usr + 0.03 sys = 0.88 CPU) @ + 113636.36/s (n=100000) Shorter Array: 0 wallclock secs ( 0.63 usr + 0.04 sys = 0.67 CPU) @ + 149253.73/s (n=100000) strftime: 1 wallclock secs ( 0.52 usr + 0.07 sys = 0.59 CPU) @ 16 +9491.53/s (n=100000) Rate Reverse Array Reference Implementati +on Shorter Array strftime Reverse Array 113636/s -- -2 +2% -24% -33% Reference Implementation 144928/s 28% +-- -3% -14% Shorter Array 149254/s 31% +3% -- -12% strftime 169492/s 49% 1 +7% 14% --

In reply to Re: datetimestamp faster/golf/prettier by Jaap
in thread datetimestamp faster/golf/prettier by Jaap

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.