Well, someone had to do it right?
I haven't played with benchmarking much, but here is my contribution..
use Benchmark; timethese (50000, { 'OPENCAT' => sub { open (INFILE, "cat mbox |"); while (<INFILE>){ #do nothing } close INFILE; }, 'OPENPERL' => sub { open (INFILE, "mbox"); while (<INFILE>){ #do nothing } close INFILE; } });
Results:

Benchmark: timing 50000 iterations of OPENCAT, OPENPERL...
OPENCAT: 287 wallclock secs (175.33 usr 19.89 sys + 46.32 cusr 44.78 csys = 286.32 CPU) @ 256.12/s (n=50000)
OPENPERL: 171 wallclock secs (168.59 usr + 2.50 sys = 171.09 CPU) @ 292.24/s (n=50000)

I dropped "system" out of it early on - due to the fact that it was at about the above levels after only 1000 iterations :-)

In reply to Re: cat vs. file handle speed? by the_slycer
in thread cat vs. file handle speed? by dorpus

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.