Author: Vincent Diepeveen
Date: 08:24:27 04/07/04
Go up one level in this thread
On April 07, 2004 at 11:19:21, Vincent Diepeveen wrote: >On April 07, 2004 at 10:48:23, Renze Steenhuisen wrote: > >> >>>>>>>I'm sure it was some implementation bug with Renze. >> >>Anyone, >> >>I only store result from the main search, so no NULL-move and no Qsearch >>results. > >Of course i store nullmove and qsearch. > >Saves me at leat 50% (if % is a good term, because it will have of course an >exponential effect in the long run). > >>I get a TT-hit ratio of 11.73%, of which a part will generate cut-offs. > >That's very high, i'm around 3-5%. posted numbers from me are the chance that hashtable gives cutoff knowing a position is in hashtable. 11.73% is very low, it will improve if you search deeper with more efficient search. >> (I call something a tt-hit when an entry is found with the same hashkey, >> draft does not need to be sufficient) >> >>the tt_retrieve code retrieves a move, which I call the TT_MOVE_SUGGESTION. >> >>could someone provide me with a % of TT_MOVE_SUGGESTIONs in a search? > >They work very well. > >>Cheers...
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.