Author: Dieter Buerssner
Date: 11:33:26 12/05/03
Go up one level in this thread
On December 05, 2003 at 13:48:41, Tim Foden wrote:
>For this position... [GLC]
> 6 37.534 +4.489 21484k Rxh6 Rxb1+ 2. Kxb1 Qfxh6 3. Qxd8 Qexd8 4. Qxc8
> Qxc8 5. Rxg8+ Kxg8 6. Qxh5 Rxa3 7. Qhxh4 Rxa2 8.
> Qxh6 Rxa4
Hi Tim, interesting statistics. Would you mind to explain some of it?
> stats: fh=96.9%/1.14%/0.674% draws=10
I think, I can guess the first number, but what do the remaining numbers (incl.
draw) mean?
> trans: probes=1282039 hits=229767 (17.92%) draft=163348 (12.74%)
Do you probe in qsearch? 21 million nodes and only 1.3 million probes; but then
again, for a 6 ply search excluding qsearch, there should be less than 1.3
million nodes?
What does draft mean? (draft stored >= current remaining depth ?)
I mainly recognized this, because in such positions, I get quite a bit a smaller
hit ratio. By default Yace probes (and stores) in qsearch. I do limit qsearch,
but a bit less than you. It needs longer to reach the depth.
77102928 3:13.9 4.97 5. 1.Rxg8+ Qfxg8 2.Rxh6 Rxb1+ 3.Kxb1 Qb7+ 4.Q3b4
Qxb4+ 5.Q4xb4 Q5xh6 6.Qxd8 Qxe1 7.Qdxe1 Qxc1+
8.Kxc1 Qxd8 9.Bxd4 Bxd5 {501}
126341037 5:13.2 4.77 6t 1.Rxg8+ Qfxg8 2.Rxh6 Rxb1+ 3.Kxb1 Q7xh6 4.Qxe8
Qgxe8 5.Qxh5 {1502}
exit
146964349 6:05.0 4.77 6u. 1.Rxg8+ Qfxg8 2.Rxh6 Rxb1+ 3.Kxb1 Q7xh6 4.Qxe8
Qgxe8 5.Qxh5 {1502}
146964349 Nodes, 98.05% Leavenodes, 402548 Nodes/sec
htable: 128250644 store, 324 rejected, 143235236 probe, 10.8% f/p, 12.0% f/s
And with probe/store disabled in qsearch:
131818955 4:34.7 4.97 5. 1.Rxg8+ Qfxg8 2.Bxb8 Nb3+ 3.Qbxb3 Qhxc1+
4.Qaxc1 Qxc1+ 5.Qxc1 {HT} {1341}
exit
163268370 5:37.1 4.97 5f. 1.Rxg8+ Qfxg8 2.Bxb8 Nb3+ 3.Qbxb3 Qhxc1+
4.Qaxc1 Qxc1+ 5.Qxc1 Qxa4H {HT} {340}
163268370 Nodes, 99.50% Leavenodes, 484273 Nodes/sec
[ ^^^^^^ ^^ Grrr ..]
htable: 78739 store, 0 rejected, 82969 probe, 12.0% f/p, 12.6% f/s
Note the few probes. I count Leafnodes only after the first level qsearch (a
first level qsearch without any further recursion will not count any leafnodes)
f/p means number found (independent of draft)/number probes
f/s: s for number of stores
> ehash: probes=0 hits=0 (-1.$%)
^^^^^ ?
In "normal" positions, I thought my f/p ratios where about as numbers I had seen
posted. But at least here, you do much better. I use a "cluster" of 3 entries
per hash-index, which has some internal structure. At store time, I basically
always replace the entry, which seems worth least. I can maximally store one
score per entry (but want to experiment with two, soon - one upper and one lower
bound).
Do you do something significantly different? Might also be interesting, what the
hit-ratio of other engines is in this pos.
Cheers,
Dieter
PS. Congrats to the nice showing of GLC in Graz
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.