Really? Has to be pretty big script to take more than a few millisec. For linux, there's a tool bundled with sources (linux/tools/perf). Far more precise and informational. 
$ perf stat perl -c -e1
-e syntax OK

 Performance counter stats for 'perl -c -e1':

          1.188739 task-clock                #    0.792 CPUs utilized          
                 2 context-switches          #    0.002 M/sec                  
                 0 CPU-migrations            #    0.000 K/sec                  
               447 page-faults               #    0.376 M/sec                  
           3499769 cycles                    #    2.944 GHz                    
           2156006 stalled-cycles-frontend   #   61.60% frontend cycles idle   
           1317972 stalled-cycles-backend    #   37.66% backend  cycles idle   
           2415287 instructions              #    0.69  insns per cycle        
                                             #    0.89  stalled cycles per insn
            488421 branches                  #  410.873 M/sec                  
             24245 branch-misses             #    4.96% of all branches        

       0.001500676 seconds time elapsed

In reply to Re^2: How can one best measure compile time of their Perl script? by oiskuu
in thread How can one best measure compile time of their Perl script? by taint

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.