When it comes to testing a multi-threaded app, there is no substitute for getting a few hours on a multiple-processor system. All your tests which you ran on the single-processor machine are valid, but only a part of the testing you'll need to do. You'll soon discover the difference between empirical evidence and proven robustness.

What's worse is that each new threading model can also affect borderline code. What worked on POSIX will have a race condition on green threads, or vice versa. Knowing your OS's threading model won't help very much from an application level: you just have to get it right, not merely apparently okay. It'll come from experience.

--
[ e d @ h a l l e y . c c ]

In reply to Re: Multi-threading in 5.8.0 by halley
in thread Multi-threading in 5.8.0 by DigitalKitty

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.