🚀 go-pugleaf

I think that pl69 has lost some speed.  It gives about the same number
of nodes per second evaluation, but it seems much much MUCH slower.
It evaluates about twice as many nodes per ply at shallow searches and
about ten times as many nodes at depths 5 and 6 ply.
I post a position below that takes 1.5 hour with pl69 versus 5 min. with pl68
to fixed depth of 6 ply.

Any ideas whats going on?

The two PL's are compiled with different options:

PL69:
OPT= -DUSEINT -DCACHE -DGDX -DHASGETTIMEOFDAY -DDEEPNULL -DQUIETBACKGROUND -DSEMIQUIETBOOKGEN -DWAY4PL64 -DHISTORY -DHASHSTATS -DAGING 

PL68:
OPT=  -DUSEINT -DCACHE -DGDX -DHASGETTIMEOFDAY -DKILLT -DDEEPNULL

and I fixed the pawn evaluation buglet posted by Kong Sian in PL69 but
not PL68.  I am sure there are many other minor differences, but nothing
I suspect as causing this.

Can HISTORY slow down the search this much.  If so, out it goes!!!

I also noticed bizarre behavior from pl69 when it encountered a mate position.
It began evaluating a 5 ply mate at 9994 (or so).  It chose to analyze another
mating move at 9991, then 9988, then 9985, then 9982, etc., counting down
by some constant offset. Weird!  So out comes this position with a 42 ply
mating move. Wow! Not! If I can gather the stats on this one I will post it
later. 

Meanwhile here's a sample to show poor timing from PL69:

post book force
e2e4 b7b6 d2d4 c8b7 f1d3 e7e6 g1f3 c7c5 c2c3 g8f6 d1e2 f8e7 e1g1 b8c6 e4e5
f6d5 d4c5 b6c5 b1a3 e8g8 a3c4 d8c7 f1d1 f7f5
depth 6 bd beep go quit

 R - - - - R K -
 P B Q P B - P P
 - - N - P - - -
 - - P N p P - -
 - - n - - - - -
 - - p b - n - -
 p p - - q p p p
 r - b r - - k -

PL68 :
-------------------------------------------------
Move# 13    Target= 0    Clock: 719805
 2.     47    5     1094   e5f6  f8f6 
 3&     41   11    13277   e5f6  d5f6  h2h3  a8b8 
 3.     41   12    15316   e5f6  d5f6  h2h3  a8b8 
 4&     45   21    37397   e5f6  d5f6  h2h3  a8b8  c1g5 
 4.     45   26    49778   e5f6  d5f6  h2h3  a8b8  c1g5 
 5&     52   55   124185   e5f6  d5f6  h2h3  a8b8  c1g5  f6d5 
 5.     52   61   136590   e5f6  d5f6  h2h3  a8b8  c1g5  f6d5 
 6&     45  120   279609   e5f6  d5f6  h2h3  a8b8  c1g5  f6d5  g5e7  c6e7 
 6.     45  176   420217   e5f6  d5f6  h2h3  a8b8  c1g5  f6d5  g5e7  c6e7 
1. ... e5f6
Gen 1645322 Node 420217 Tree 495 Eval 41721 Rate 2387 EC 28047/10920 RS hi 0 lo 0 
Hin/Hout/Tcol/Coll/Fin/Fout = 1791/820/0/0/0/0
My move is: e5f6

<<<<<<ALL THIS TOOK ABOUT 3 MINUTES, 420k NODES>>>>>>>>

PL 69:
-------------------------------------------------------
Your move is? 
Move# 13    Target= 0    Clock: 719697
 2.     42    1     2349   e5f6  e7f6 
 3&     36    4    10405   e5f6  d5f6  h2h3  a8b8 
 3.     36    5    13150   e5f6  d5f6  h2h3  a8b8 
 4&     40   24    68984   e5f6  d5f6  h2h3  a8b8  c1g5 
 4.     40   33    92511   e5f6  d5f6  h2h3  a8b8  c1g5 
<<<after a few minutes I lost patience and hit ^C>>>
 5.     40  209   661512   e5f6  d5f6  h2h3  a8b8  c1g5 
1. ... e5f6
Gen 2478550 Node 661512 Tree 962 Eval 44247 Rate 3165 EC 32519/9718 RS hi 0 lo 0 
Hin/Hout/Tcol/Coll/Fin/Fout = 125289/13345/0/0/0/0
My move is: e5f6
Your move is? 

<<<<<<<<<ABOUT 5 MINUTES SO FAR, 661k NODES, NOT YET 5 ply>>>>>>>>
This thing runs for another 1.5 hour at least if I let it go.


Mike