I see lots of "solutions" being tossed around here on a presumption of what the actual problem is. IS the source of the performance issue ACTUALLY the overhead of launching a new Perl? If the program blindly launches a new subprocess with every request, the problem might simply be "thrashing." Maybe the application needs a way to put a cap on how many children are running at a time. You say that most of the scripts are trivial, but how many are run most often? Are any of them actually expensive? You need log files that you can analyze to see what the bottlenecks actually are. Guesses won't get you answers.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|