On Wed, Jul 9, 2008 at 1:16 PM, Eric Wilhelm <[EMAIL PROTECTED]> wrote: > Once I get around to checking-in these changes, the following becomes an > option: > > ./Build test --tap-harness-args jobs=29 --use-tap-harness > > Unfortunately, that only cuts the test time from 22 to 15s for me. I > notice that t/compat.t is using 8s, most of which is spent doing the > same steps in different variations.
Last time I profiled that test, a huge portion of the time was spent getting the CWD over and over again. Perhaps that could be done better? -Ken
