Computer Chess Club Archives


Search

Terms

Messages

Subject: Re: Comet captures its own King at e1 of 5th game in Comet-Crafty match

Author: Ulrich Tuerke

Date: 10:19:08 05/28/98

Go up one level in this thread


Meanwhile, I have a very natural explanation for the observed problem.
KK has probably overdone with the hash tables. From the debug data, I
have seen that Crafty had allocated 53 MB hash tables and Comet 32 MB.
I guess, this was too much for the platform the match was running on.
On platforms with virtual memory management (like WIN-32), processes
will be swapped out to the hard disk when shortages of memory occur.

Assumed that the Comet engine had been swapped out of the memory in
the moment where Crafty was resigning, then it could take seconds to
reload the program and may be winboard's timer had the chance elapse.
May be some of the users don't realize how dangerous it is for a chess
program to overdo with the hash tables. It's better to allocate less
to be on the safe side.

Regards, Uli



This page took 0 seconds to execute

Last modified: Thu, 15 Apr 21 08:11:13 -0700

Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.