Fork makes a copy of the current running perl program and then you make your system call. That child has to wait around for the system call to finish which is why you are seeing 16 copies, and you should also see the 16 commands running.
BUT there is no reason to panic, as fork is designed to be efficient as possible and will share pages where possible.
The help says :-
On most systems supporting fork(), great care has gone into making it +extremely efficient (for example, using copy-on-write technology on data pages), making it + the dominant paradigm for multitasking over the last few decades. )
Look at the total memory usage which is displayed on the first few lines of the top output and you'll see that there's plenty of memory really.
In reply to Re: Parallel::ForkManager Memory issue
by RichardK
in thread Parallel::ForkManager Memory issue
by hotel
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |