My impression is that the core threading code is fairly stable. However, many popular Perl modules are not yet thread safe - DBI is one that I know of. Most pure-Perl modules will be thread safe out of the box but most XS modules will not be, particularily if they access non-thread-safe C libraries underneath.

As far as fork()-vs-threads the main difference is in how the processes communicate. With fork() you can communicate using pipes but it is far from convenient. Threads can share() variables and communicate quickly and easily. Also, under some operating systems threads can be created with lower overhead than fork().

-sam

In reply to Re: Status and usefulness of ithreads in 5.8.0 by samtregar
in thread Status and usefulness of ithreads in 5.8.0 by BazB

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.