Your answer, besides being almost completely wrong as usual (apache can be tested offline, PSGI is deployment agnostic so FCGI is an incorrect assertion, the processes are not lightweight, code conversion is not necessarily easy, and worker processes can be ruined or hanged, especially in an apache FCGI process, with application code), amounts to: "Change your technology stack completely." But at that point the error will not be solved. Deployment changes do not fix code issues. I'm really starting to wonder if the ones with valid lawsuits in all this, since it's a topic you like to revisit now and then, might really be the clients you've bilked with your advice.

In reply to Re^2: Apache becomes unresponsive running mod_perl by Your Mother
in thread Apache becomes unresponsive running mod_perl by Anonymous Monk

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.