I think it's worth mentioning in your POD that it's wisest to test code both with and without forking enabled, if your platform supports it. Enabling forking is a better test of each piece of code, but disabling forking is a better test of how they interact in a real script.

One might even go so far as to say that differences between the two sets of results should throw up yellow flags. (Maybe expected, maybe not, but certainly the place where algorithm analysis should be focused.) The average scripter may need you to include this short summary of your original point. ;-)

BTW, I love the title for this thread. Almost, but not quite, vulgar. :-D

In reply to Re: Forking Benchmarks? by Rhys
in thread Forking Benchmarks? by simonm

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.