Simple: Perl was most likely being run as CGI. It shows tremendous ignorance to compare Perl running through CGI to Java servlets. Java running through CGI is much slower than Perl. Perl running through mod_perl or FastCGI is just as fast as Java servlets.

It's also possible that the Perl code was awful, written by people who have never heard of CPAN or profiling, but the biggest hit is typically CGI.

Remember, Amazon.com runs large amonts of its site on Perl with FastCGI, and so does Ticketmaster.com (on mod_perl). It's well-established that Perl has good performance.

In reply to Re: Perl verus Java by perrin
in thread Perl verus Java by punchcard_don

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.