one "DO" comes immediately to mind as I have dealt with it recently with a system that went from reasonably few transactions (departmental) to high volume (enterprise wide usage).

If using a database, create as few connections as possible. DB connections are expensive and in a high transaction CGI (as well as non-CGI) scenario, creating multiple connections where less (one is best) will do will have a significant impact on your response time, as well as anyone else you may be sharing db resources with (like listeners).

Of course this suggestion (as well as many others you may receive on this) is really valid for all languages.

In reply to Re: Does anyone have a list of 'donts' when optimizing? by wardk
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.