Re: TB2::Mouse will be internal use only... with one hitch.

On Tue, Nov 29, 2011 at 10:33:42PM -0800, Michael G Schwern wrote:
> On 2011.11.29 9:49 PM, David E. Wheeler wrote:
> > How much slower will this make running the core tests,
> > since neither Mouse nor Mouse::XS will every be available
> > there (during development, at core installation time).
> 
> Doing some back of the envelope calculations, it looks like an extra minute
> and a half on my laptop.  I don't know how long core tests take right now.
> 
> Running...
> 
>     use Test::More tests => 1;
>     pass("ok");
> 
> 100 times via prove...
> 
> With 0.98:  2.2s
> With 1.5:   10s
> 
> An extra 8 seconds per 100 tests.  There's about 1100 core tests which use
> Test::More.  8 seconds x 11 is about 90 seconds.

Divide by the number of CPU cores.
Assuming one can hog them all, what probably matters is the duration of
the IO::Compress tests.

My laptop takes about 20 minutes to Configure, build and test the core.

dromedary and various other multicore servers I have access to usually take
about 5 minutes. Upshot - it saves a lot of time to hack locally, then
rsync the code off to a different machine to actually run the complete tests.

> That's worst case.  I can probably get compile time down at least 20ms which
> shaves off about 30 seconds.

The IO::Compress tests being such a reliable serial bottleneck that I can set
off a complete build and test run while writing this e-mail just to check
that I had the right distribution, and it finishes before me :-)

Nicholas Clark