What is the best memory allocation for Bringer?
For 16Mb RAM , the author suggests using 10/2/2 [Position/Evaluation/Pawn] allocation and another 2 Mb for Tablebases caches. For allocating 32 Mb RAM a 20/4/4 Split might be best. You could also try optimising the memory allocation yourself, but this requires some understanding and monitoring of the line “Hash% Pos: 1%/5%, Eval 53%/16%, pawn 99%/80%” etc in the program. ‘Hash% Pos 1% / 5%’ means : the positional hashtables are 1% filled, and 5% of the ‘probes’ were successful (a transposition was detected). Note that the remaining 95% of the probes were not useless, they improve the move ordering. The other values mean the same thing: ‘filled percentage’ / ‘percentage of successful probes’. Note: when you try to optimise Hashtables size, pay attention to the second value: if you double (for example) the size of the Hashtables, and the ‘percentage of successful probes’ increase from 80% to 82%, the gain is only 2%. Typical values for the ‘percentage of successful probes’ in the middleg