A lot of my work is in a web application environment. There, Perl's threading or forking or what-have-you isn't really relevant. Apache spawns processes for multiple requests, and the database spawns threads to handle them. I get the benefit of many CPUs essentially for free.
In back end code, when I want to really max out the machine, I generally write things so that more than one can run at a time and then run as many as I want. I have to think about it a little more, but not much.
I can imagine there could be situations where an individual request would benefit from being spread across as many CPU instances are available, and the "natural" solution just doesn't do that. Still, I think that will be the exception rather than the rule.
-
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.
|
