A little help with child processes.

[Rech]

Yes I know, but the CPU-intensive tasks eat a lot of memory and for 
weird reasons they don't free it (I know bad programming, but re-writing 
all the code is impratical at this point). Running them in child 
processes solves the problem because when a child dies it frees all the 
allocated memory.

Andrea.

 
In article <voidnXFxAoCxw03d4p2dnA at comcast.com>,
 "Larry Bates" <lbates at swamisoft.com> wrote:

> Unless you are going to start more than one child
> process in parallel and there is enough I/O to
>  make it worthwhile, there's no reason for using
> child processes at all.  Just program the application
> as a single loop.  You can't speed up CPU bound
> applications with child processes.
> 
> HTH,
> Larry Bates
> Syscon, Inc.