First, it's not the weight of the subprocess, it's the number of invocations that would be problematic. Second, since you are only running your code once, there are all sorts of problems with your benchmark. Use
Benchmark to actually test performance.
#!/usr/bin/perl
use strict;
use warnings;
use Benchmark qw(:all :hireswallclock) ;
cmpthese(20, {
'Backtick' => sub{`echo plenty of fish` for 1 .. 10},
'Open' => sub{for (1 .. 10){open my $fh, "echo plenty of fish |";
+<$fh>}},
});
outputs
Rate Open Backtick
Open 9.29/s -- -1%
Backtick 9.35/s 1% --
on my Windows box and
Rate Open Backtick
Open 85.8/s -- -10%
Backtick 95.7/s 11% --
on a Linux server (with iteration count upped to be meaningful).
As an aside, if you are optimizing away milliseconds of overall run time, you probably shouldn't be using Perl.
#11929 First ask yourself `How would I do this without a computer?' Then have the computer do it the same way.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.