Automatic speed testing #8
Description
Implement some way to measure the overall speed of the program.
While partial component testing can be done before we integrate it into the
engine, sometimes attenuating factors come into play and we need to measure
if it makes a speed improvement or not (and how big it is)
We could make the tester evaluate each intermediate board of a recorded
game and report the summed up time it took to evaluate the whole game. But
don't let the engine make a move. This way, the recorded game stays the
same even if we change the scoring logic. Just evaluate, make recorded
move, evaluate, make recorded move, etc..
We can enhance it to remember the time of each move and create fancy
statistics. But later on.
Original issue reported on code.google.com by Valentin Stanciu on 25 Jun 2009 at 12:39