The --fork option
Andy Armstrong
andy at hexten.net
Fri Mar 6 16:33:49 GMT 2009
It seems that the --fork switch hasn't worked for about six months -
and, while it would be possible to get it working again, it'd be hard
and ugly. The main problems are that
1. Parallel::Iterator uses Storable to pass jobs to the forked
harnesses, jobs now contain coderefs and Storable can't (adequately)
serialise coderefs.
2. The new factory stuff doesn't play nicely with forked harnesses and
I can't see a clean way to make it work.
Given that --fork is only faster than -j in contrived tests does
anyone mind if I remove the --fork option and associated code?
--
Andy Armstrong, Hexten
More information about the tapx-dev
mailing list