Author: Ed Trice
Date: 18:22:51 06/23/04
Go up one level in this thread
> >Crafty is a pretty fast searcher (from a pure NPS perspective on my machine) and >the evaluation code it appears has minimal impact on it's speed. I have toyed >with turning most of evaluate code off and I came close to a ~8% (it's been a >while) increase in NPS. For 8% NPS cost, the evaluate code is well worth it. Sometimes you can get a node/second increase as a result of doing something bad. For example, if you alter the code in such a way to affect the move ordering, you can bloat the game tree (a bad thing) but gain an increase in speed (a good thing, but not at the cost of increasing the size of the tree.) Conversely, can you do something bad that will prune the tree (say return more scores that are identical, so that the > criterion for PVS passes it as a candiate replacement move when in actuality the score should be higher and the move choice should be replaced), but get better time-to-depth performance. You have to understand what you have done as a result of making changes, which is very hard since this stuff is huge in quanitity and pretty much invisible.
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.