Author: Bob Durrett
Date: 06:26:35 12/01/02
Go up one level in this thread
On December 01, 2002 at 04:35:09, David Rasmussen wrote: >On November 30, 2002 at 23:40:30, Robert Hyatt wrote: > >> >>And some have reported no speedup for DF as well, but I don't worry since I >>don't have anything to do with that program. But as far as "does crafty have >>trouble with AMD?" or "does AMD have trouble with Crafty?" the two questions >>are identical... >> > >Sure, but that doesn't mean that a program like Crafty couldn't be made to run >as fast on Athlons as on P4's, or faster. It is your design choice. There is >nothing that makes it harder on the Athlons than on the P4. You've chosen to >make them faster on P4. > >/David The thrust of this conversation seems to run counter to the Crafty v18.11 Benchmark comparison posted here recently. AthlonXP 2.52GHz was shown to have Kn/s much higher than P4-3.25GHz. Unfortunately, we were not given particulars regarding the computer(s) and memory type(s) used in the comparison. Maybe the memory type explains everything? Could it be that AMD runs chess engines best using one type of memory whereas Intel processors run best with another type of memory? This thread seems to suggest that the dominant factor is "compatibility" of the Crafty software with the different types of processors, rather than memory type. Implied is that other chess engines might have the opposite compatibilities, with Intel being favored for one engine, AMD best for another, and some engines running equally well on either. Obviously, a commercial program must run well with all commonly used processors, but Crafty is not commercial. To complicate matters, it may [?] be that some chess engines do better with one type of memory and others do best with another kind of memory. Then there is that "multi-threading stuff" to furthur complicate this issue. How to sort out this mess??????? Bob D.
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.