comment on

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.

Cheers.

BazB

In reply to Status and usefulness of ithreads in 5.8.0 by BazB

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Clear questions and runnable code get the best and fastest answer
	PerlMonks