Performance regression in unit test suite

[al-maisan]

The run time of the unit test suite quadrupled.

The following bash script was run last night on gemsun02 in order to exercise the test suite: http://paste.ubuntu.com/591606/.

According to the results (http://paste.ubuntu.com/591605/) the following change set caused the runtime of the unit test suite to quadruple:

commit bf18813219abd2ccae5254e9e92d9e6aa97982e8
Author: root <root@roundabout.(none)>
Date:   Fri Apr 8 08:33:20 2011 +0000

    Squashed commit of the following:

    commit b2bb2994e353c9f7e4b4d4ab55326bfed992a09d
    Author: Damiano Monelli <monelli.damiano@gmail.com>
    Date:   Mon Mar 21 16:44:04 2011 +0100

        added opensha-lite corrected for area source bug

[al-maisan]

https://www.pivotaltracker.com/story/show/12108505

[ChristopherMacGown]

git already has functionality to determine when a regression was introduced, please see the manpage for git bisect...

[al-maisan]

Hello Chris, thanks for the hint -- will take a look.

[al-maisan]

OK, had a look at git bisect. I don't think it's the right tool for this particular job since it is interactive in nature and automating it would probably take the same amount of time as writing the bash script I used in this instance.

Just my $ 0.02

[larsbutler]

This is no longer an issue.