Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options
 
PerlMonks  

Re: Design advice: Classic boss/worker program memory consumption (PipeWorkers)

by tye (Sage)
on May 20, 2014 at 20:27 UTC ( [id://1086857]=note: print w/replies, xml ) Need Help??


in reply to Design advice: Classic boss/worker program memory consumption

I need to upload IPC::PipeWorkers to CPAN. It handles Solution 2 quite efficiently.

One down side is that you can't fork a replacement child when one of your worker children dies. That motivated me to consider exactly your Solution 1. I spent a little time trying to work out the details of that. But I ended up abandoning the idea because of the huge increase in complexity involved.

Worker children disappearing turned out to never be much of a problem in practice. Also, it is wise for long-running daemons to periodically be restarted anyway, which means the rate of child death needs to be pretty high for it to end up mattering much.

- tye        

  • Comment on Re: Design advice: Classic boss/worker program memory consumption (PipeWorkers)

Replies are listed 'Best First'.
Re^2: Design advice: Classic boss/worker program memory consumption (PipeWorkers)
by shadrack (Acolyte) on May 20, 2014 at 20:51 UTC
    It handles solution 2 quite efficiently.
    How? Just in general, what's your strategy?

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://1086857]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (4)
As of 2024-04-19 13:13 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found