Parallelizing the test suite

Some very superficial experiments [1] seem to show that running
multiple tests in parallel can give a reasonable speedup. Somebody
with more free time than myself may want to look into (optionally)
running tests in parallel, either at the level of running several
python scripts at the same time, or more likely making the test runner
fork itself. It's not trivial (organizing the success and failure
results being the hardest part) but it could speed up the test suite,
which is always a good thing. (Not to mention potentially finding
weird server concurrency bugs.)

--dave

[1] Specifically, timing "./prop_tests.py & sleep 1; ./diff_tests.py"
vs "./prop_tests.py; ./diff_tests.py", which took 1m44 and 2m20s
respectively. They do fight a little over the Greek repo in the
former.

-- 
David Glasser | glasser_at_mit.edu | http://www.davidglasser.net/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org