I'm hearing a bell in the back of my head, along with a quote about how premature optimization is the root of all evil.

Since you're converting these from shell scripts, I doubt you really need them to be efficent. Make them easy to understand and add efficency later if you really need it.

That said, if you want to test how long a certain block of code takes to execute, try this (untested):

my $start_time = times();

# Bunch of code here

my $end_time = times();
my $run_time = $end_time - $start_time;
print "Took $run_time sec\n";

[download]

Higher granuality clocks are also available (like Time::HiRes).

In reply to Re: Benchmarking shell script conversions by hardburn
in thread Benchmarking shell script conversions by Limbic~Region

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.