I use iThreads in productions systems, no ongoing problems (running 2-5 months, ~900k requests)... YMMV.

You'll need to:

I mostly use Thread::Queue to communicate between a reusable pool of threads. I try not to use shared variables (so I don't have to reason about what is/isn't shared). I make sure not to allocate *anything* I don't have to in the "parent" thread.

There certainly are still some problems. There's no other option on Win32; fork() there is an emulation using iThreads which breaks other things (so you shouldn't use it).

I'm sure others will have war stories... I've got what I needed to done without too many problems... mostly working around cloning and file-handle DESTROY issues.

-David

In reply to Re: Stability of threads in perl 5.8? by erroneousBollock
in thread Stability of threads in perl 5.8? by bowei_99

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.