Article View: gnu.chess
Article #2232Re: History Mechanism in gnchess sort routine.
From: Dan Oetting
Date: Tue, 31 Oct 2000 17:02
Date: Tue, 31 Oct 2000 17:02
17 lines
1493 bytes
1493 bytes
In article <39FEE9B4.ECC5CAEC@wretched.demon.co.uk>, Simon@wretched.demon.co.uk wrote: > I've been looking at gnuchess 5 sort.c >... I'm finding cutting anything seems to > give performance benefits, which I suspect are due to better use of the > CPU cache - so other peoples results may vary depending on processor. >... > BTW these gains are very minor - less than 5% on nps - so hard to > measure accurately. The whole idea of move sorting is to find the best move sooner and therefore reduce the node count with alpha-beta cuts. You cannot measure the effects of move sorting by looking at nps, you need to look at time to ply. -- Dan O.
Technical Details
Message-ID:
<dan_oetting-CDCF83.10022831102000@news.dnvr.uswest.net>Path:
arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!sn-xit-03!supernews.com!hermes.visi.com!news-out.visi.com!news-out.uswest.net!news.uswest.net.POSTED!dan_oettingReferences:
<39FEE9B4.ECC5CAEC@wretched.demon.co.uk>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10d71d,89011c5d09fe6259 X-Google-Attributes: gid10d71d,public X-Google-ArrivalTime: 2000-10-31 09:02:32 PST Path: arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!sn-xit-03!supernews.com!hermes.visi.com!news-out.visi.com!news-out.uswest.net!news.uswest.net.POSTED!dan_oetting From: Dan Oetting <dan_oetting@uswest.net> Newsgroups: gnu.chess Subject: Re: History Mechanism in gnchess sort routine. References: <39FEE9B4.ECC5CAEC@wretched.demon.co.uk> User-Agent: MT-NewsWatcher/3.0 (PPC) Message-ID: <dan_oetting-CDCF83.10022831102000@news.dnvr.uswest.net> Lines: 17 Date: Tue, 31 Oct 2000 10:02:28 -0700 NNTP-Posting-Host: 63.225.125.105 X-Trace: news.uswest.net 973011748 63.225.125.105 (Tue, 31 Oct 2000 11:02:28 CST) NNTP-Posting-Date: Tue, 31 Oct 2000 11:02:28 CST