To echo talexb, be very wary of premature optimization; you can waste an obscene amount of time optimizing things that you know to be relatively inefficient but pale in significance against less obvious bottlenecks in your CGI.

Anyhoo, searching for 'optimization' turns up a fair amount of nodes, and I'm sure Super Searching would turn up even more, but two nodes (RFC CGI.pm refactoring and CGI::Simple vs CGI.pm - Is twice as fast good enough?) that might be of particular interest ...

    --k.


In reply to Re: Re: Does anyone have a list of 'donts' when optimizing? by Kanji
in thread Does anyone have a list of 'donts' when optimizing? by BUU

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.