Tag: Cache

Quoting from my Pull Request #12: Converted Cache class’ _positions field from a jagged array to a flat array. The flat array is more memory efficient than a jagged array. Jagged arrays have a .NET object header for each sub-array (for garbage collection tracking of reachable-from-root). This enables more positions to be stored per megabyte of memory. The code in this PR stores 65,536 positions per MB = 8,388,608 positions for a typically sized 128 MB cache. Added stats to track cache hit %, best move found in cached position %, and count of invalid best moves. Stats are displayed… Continue Reading