I have made a switch from cgi to mod_perl and memory is the least of my problem. My mod_perl application is now sized at 50M per process. That is 20 processes per server with 1G memory each.

With the current normal memory size on servers ranging above 1Gb, you don't need to worry about your process sucking all the available memory. The only time you need to worry about running out of memory is when your application needs to process a really large data set, which needs to be in physical memory at the same time.

If you really worried about your perl code unintentionally kill the OS by using up all the available memory, you might want to read about OOM killer on Linux.

-cheepy-

In reply to Re: How to tell if script sucks...memory by badaiaqrandista
in thread How to tell if script sucks...memory by jriggs420

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.