Author: Komputer Korner
Date: 20:26:37 05/28/98
Go up one level in this thread
On May 28, 1998 at 13:19:08, Ulrich Tuerke wrote: >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 The above is false. If you check the Comet.ics file you will see 48Mb of hash for Comet. I can't help it if Comet doesn't have pawn hash tables. So this match up of 48 Mb hash for Comet and 48Mb main hash + 5 Mb for pawn hash tables for Crafty is fair. I am testing on a WIN NT 4 system with 144Mb so nothing is getting swapped to the hard drive. -- Komputer Korner
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.