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.

In reply to Re: Multi-core and the future by kyle
in thread Multi-core and the future by pileofrogs

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.