Author: Mike Byrne
Date: 17:06:06 06/23/04
Go up one level in this thread
On June 23, 2004 at 19:52:45, Ed Trice wrote:
>On June 23, 2004 at 18:30:57, Russell Reagan wrote:
>
>>I am curious about a few design choices in Crafty. Some of the questions are
>>general questions that anyone who is knowledgable could answer, so I ask this
>>publicly instead of via email to Dr. Hyatt.
>>
>>First issue. Crafty is written with a lot of color-specific code, like:
>>
>>if (wtm) {
>> // ...
>>}
>>else {
>> // ...
>>}
>>
>
>If you profile Crafty, you will find something like only 11% of the computation
>is spent on the evaluation routine. Say you were to make this code execute twice
>as fast. Then, overall, the entire program would be only 5.5% faster.
>
>To make a big performance gain, you have to attack the bottlenecks.
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.
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.