As far as win32/un*x comparisions go, I've seen benchmarks according to which linux process were faster then win32 threads.

With threads==lighter processes on un*x you get maybe 0.5% improvement, while programming/debugging becomes way harder (maybe not for java addepts, who are raised with 'threads are god/good' mentality).

Thus, I think, efficency is not a good reason for such strange feature, locality of data, maybe, wider availability of Niagara-like processors, maybe.

And with perl threading stabilising ( for me one such sign is new debian stable shipping threaded perl by default ), we should be ready for technologies like SMT.

In reply to Re^2: Threading vs perl by Eyck
in thread Threading vs perl by Eyck

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.