[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gnugo-devel] GNU Go 3.3.23

From: Marco Scheurer
Subject: Re: [gnugo-devel] GNU Go 3.3.23
Date: Wed, 16 Jul 2003 20:10:45 +0200

On Wednesday, July 16, 2003, at 07:54 PM, <address@hidden> wrote:
On my Mac, "time make regression" gives the following results:

3.3.23  1050.970u 5.850s 23:24.91 75.2% 0+0k 1+23io 0pf+0w
3.2     1249.210u 6.040s 24:16.30 86.1% 0+0k 0+23io 0pf+0w

All this using the defaults compile and run options. However, I'm not
sure it proves anything since the regression tests themselves have
changed. Is there a constant benchmarking test?

Are you are using the 3.2 testsuite with 3.2 and the 3.3.23 testsuite
with 3.3.23? If so I am surprised that 3.3.23 shows less user time
than 3.2.

The reason this is surprising is that there are MANY more tests in
3.3.23 than in 3.2. The long fifth batch consists of new tests. The
first four batches are mainly old tests. I suppose I should go back
and run the 3.2 regressions and see how long they take.

But make regression only does the first_batch isn't it?

I only gave a quick look to the differences between 3.2 and 3.3.23 regression tests. It's hard to tell which is longer. I'm going to try to switch executables and regression tests, but then I would expect some tests to fail.

I'm confused by the fourth column 23:24.91. That would seem to be
the elapsed time but not that many hours have elapsed since the
3.3.23 release.

I think it is minute:seconds:hundredth...

I gather that make regression is not enough to make sure everything is OK, and I'll also run a make test tonight.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]