in reply to Parallel::ForkManager eating up Resources?
Ouch. 140 children all with their own DB connections? And you create a new connection per child? Surely there is a better way.
First off, you should probably cut down the number of children. Most database performance numbers fall off pretty quickly when you start adding a number of children doing anything more than reads.
You should also look at using a pool of database handles. Why create and then close database connections over and over again if you don't have to? I sped up the performance of a data loading script by a few orders of magnitude by moving the dbh create/destroy outside of the main loop.