Barring the limitations listed in perl-5.8.0-RC3's perldoc threads, threads::shared and perlthrtut, what status is Perl's current threading implementation considered to be?
As of 5.6.1 it was experimental, but I cannot see any such warnings in 5.8.0. Are they now considered production quality, or just not quite so experimental as to be labelled as such?
I've read some of the earlier articles discussing fork() and Threads (now superceded by threads), but does Perl's current thread implementation offer the benefits of threading against just using fork() and spawning full child processes?
From a design and resource usage point of view, could someone please give some conditions where threading is considered preferable to fork()'ing?
I use fork a fair bit in order to process very large chunks of data in parallel, but I'd be interested to see if threading this sort of thing has any benefits.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||