Perl is not designed to be as fast as possible on computers. It's designed to be fast enough on computers, and as fast as possible on the human writing the program. Sometimes using a strictly compiled language will save CPU time compared to a Perl alternative; sometimes not. The Perl program, however, will almost always be easier to write, debug, maintain and extend. And Perl itself is written in very fast C, so the speed hit is not as hard as you might think.

Regarding your CGI example, there are ways to avoid the performance hit of spawning a new interpreter for each request; mod_perl is the most popular.

Finally, your comment about "other better options are out there" seems to indicate you have your mind made up already...

In reply to Re: speed factor by gamache
in thread speed factor by hashin_p

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.