The speed issue is not as bad as it sounds. CGI uses several tricky methods to defer compilation until absolutely necessary. In addition, if you use the object-oriented interface, you can save the time required to import several dozen symbols.

If you use only what you need and code reasonably good code, you can probably handle a hundred thousand hits per day. Depending on what you do, CGI::Lite may be a better approach.

The bottleneck may instead be the cost of spawning new processes, in which case a properly set up mod_perl will indeed give bigger benefits. It's still a little experimental on NT, though.

In reply to Re: CGI.pm: what of it? by chromatic
in thread CGI.pm: what of it? by Donzo

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.