[IPython-dev] Slow testsuite?
Wed Feb 22 00:32:56 CST 2012
Much of the reason the parallel test suite is slow is that it starts
engines at many points, since numerous tests involve the behavior during
changes of the number of engines. Further, the reason the test suite has
become slower is the recent increase of the default heartbeat period from
1s to 3s. This means it can take 6s from starting an engine to the Hub
confirming that the engine is up on its first heartbeat response. I can
shorten the heartbeat time in the test suite quite easily (via the `--ping`
argument to the controller). It's still slow, due to the starting of many
processes, and various waiting periods, but adding `--ping=100`
(milliseconds) to the controller args, shaved ~60s off my runtime.
Very nearly all of the time in the parallel test suite is spent waiting for
something or other, so a fast machine will make approximately no difference.
On Tue, Feb 21, 2012 at 17:07, Jörgen Stenarson <
> Fernando Perez skrev 2012-02-21 20:00:
> > On Tue, Feb 21, 2012 at 10:49 AM, Jörgen Stenarson
> > <firstname.lastname@example.org> wrote:
> >> How long does the testsuite take to run on an average linux machine? On
> >> my windows machine it takes 125s with 100s for the parallel stuff. Is
> >> that normal? The reason I'm asking is that I think the running time for
> > On my fairly new and fast linux desktop, I get nearly identical results:
> > IPython test group: IPython.parallel
> > Ran 121 tests in 98.502s
> > ...
> > Ran 10 test groups in 125.719s
> Ok good to know, then there isn't anything wrong in my setup.
> IPython-dev mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the IPython-dev