in reply to To Fork or Not to Fork. Tis a question for PerlMonks

Depends what the forked code does. CPUs and memory as a rule are way faster than disk IO. If there's a lot of processing to be done, forking (or threading) means grabbing more processors. If you're IO bound, then it probably won't help much - any gains are offset against contention.

  • Comment on Re: To Fork or Not to Fork. Tis a question for PerlMonks