Beefy Boxes and Bandwidth Generously Provided by pair Networks
XP is just a number
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??


Description
Parallel::ForkManager automates the sometimes tedious process of running multiple parallel forks from a script. It also allows you to control how many forks run at once, and keeps that many running, which simplifies a rather complex task. It is extremely simple in operation and well documented.

Who should use it?

Anyone who wants to implement forking in a script. I wrote a fair bit of forking code before discovering this module, and I must say, I don't think I'll go back. It makes life much easier, and isn't that what good perl modules are supposed to do?

Who should NOT use it?

There are some forking scenarios which are probably too complex for it, although I haven't found any of those myself yet. It might be difficult to use for socket server applications, since controlling the timing of the forks could be tricky. Or fun, depending on your perspective.

Documentation

Excellent - clear examples and concise wording. Even I understood it.

Personal Notes

I've converted almost all of my old fork code to run with this module. It took just minutes, and performance improved (I was spawning forks N at a time, waiting for them all to die, and then spawning N more. This thing keeps N forks running all the time without Ne+02 lines of code ;-). Highly recommended!!

In reply to Parallel::ForkManager by Clownburner

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others surveying the Monastery: (3)
As of 2024-03-29 02:22 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found