That might also depend on your architecture, as my 5.8.8 doesn't show thos huge differences on Linux, but YMMV:

v5.8.8 built for x86_64-linux Rate class_nodot class literal class_nodot 865566/s -- -17% -19% class 1047607/s 21% -- -2% literal 1068831/s 23% 2% -- v5.11.0 DEVEL33542 built for x86_64-linux-thread-multi Rate class_nodot literal class class_nodot 782508/s -- -9% -10% literal 861502/s 10% -- -0% class 865566/s 11% 0% -- v5.10.0 built for i686-linux-64int Rate class class_nodot literal class 808928/s -- -2% -17% class_nodot 822085/s 2% -- -15% literal 969189/s 20% 18% -- v5.8.8 built for i686-linux-64int Rate class_nodot class literal class_nodot 3937/s -- -23% -100% class 5111/s 30% -- -100% literal 1065584/s 26967% 20750% -- v5.8.7 built for i686-linux-64int Rate class_nodot class literal class_nodot 2576/s -- -32% -99% class 3811/s 48% -- -99% literal 340787/s 13131% 8841% -- v5.8.7 built for IA64.ARCHREV_0-LP64 Rate class_nodot class literal class_nodot 2169/s -- -18% -100% class 2646/s 22% -- -99% literal 463693/s 21282% 17425% -- v5.11.0 DEVEL33495 built for IA64.ARCHREV_0 Rate class_nodot literal class class_nodot 435916/s -- -9% -10% literal 480089/s 10% -- -1% class 483507/s 11% 1% -- v5.10.0 built for IA64.ARCHREV_0 Rate class_nodot class literal class_nodot 233984/s -- -8% -8% class 254449/s 9% -- -0% literal 254481/s 9% 0% -- v5.10.0 built for IA64.ARCHREV_0-LP64 Rate class_nodot literal class class_nodot 269216/s -- -9% -10% literal 296479/s 10% -- -1% class 299316/s 11% 1% -- v5.8.8 built for PA-RISC2.0 Rate class_nodot class literal class_nodot 852/s -- -26% -100% class 1146/s 34% -- -100% literal 328648/s 38456% 28589% -- v5.8.8 built for PA-RISC2.0-LP64 Rate class_nodot class literal class_nodot 901/s -- -35% -100% class 1393/s 55% -- -100% literal 326127/s 36080% 23315% --

++ for this post BTW. PBP is to make you think, not to apply everything blindfolded. This is one of them.


Enjoy, Have FUN! H.Merijn

In reply to Re: The cost of unchecked best practices by Tux
in thread The cost of unchecked best practices by moritz

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.