Does that mean that the cases are run serially (as in the original Benchmark approach) -- that is, case #2 doesn't start until case #1 is finished?

Correct, the cases are run serially, with the parent process waiting for the forked child to complete the timing cycle before it proceeds.

I don't have any experience using a two-arg open where the second arg is "-|" -- perdoc -f open doesn't discuss this usage directly

You may need to just look harder... 

  If you open a pipe on the command '-', i.e., either '|-' or '-|'
  with 2-arguments (or 1-argument) form of open(), then there is
  an implicit fork done, and the return value of open is the pid
  of the child within the parent process, and 0 within the child
  process. (Use defined($pid) to determine whether the open was
  successful.) The filehandle behaves normally for the parent, but
  i/o to that filehandle is piped from/to the STDOUT/STDIN of the
  child process. In the child process the filehandle isn't opened--
  i/o happens from/to the new STDOUT or STDIN.

[download]

I'll update the comments to mention this, and fix the documentation nit you pointed out. Thanks for the feedback!

In reply to Re^2: Forking Benchmarks? by simonm
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.