If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post and use all the features of the Chess2U forums. To start viewing messages, select the forum that you want to visit from the selection below.

GAME 40 - Stockfish shatters the opening tranquility with a bishop sac on h7. After castling on the queenside, Stockfish then throws its forces into attack down the f-file, which Komodo has kindly opened up. When the smoke finally clears, Komodo has survived the onslaught by walking the king over to b8, but now faces connected passed pawns on the g and h files. Fortuitously,once the a8 rook comes out via a6 and the queens come off, Komodo is able to hold the resulting endgame and salvage a draw. So we're now heading down the home straight in this match and it's still locked up at 2-2!

GAME 41 - Despite both sides castling short, Stockfish advances on the kingside. However, with Komodo holding off any threat there, Stockfish walks its king away and cedes control of the h-file in order to create connected passed pawns on the queenside. Komodo manages to hold the draw though, due to the exposed position of the Stockfish king.

GAME 42 - with reversed colours, Stockfish starts making overtures on the queenside, but is held in check somewhat by having to keep an eye on its kingside. Control of the open b-file exchanges hands a few times, then most pieces come off leaving a drawn queen and pawns ending. Still 2-2, with an incredible 38 draws.

Game 43 - another game where a lot of pieces came off very early, and with both engines having a lot of time left on the clock. Komodo started hitting tablebases very very heavily, the O/S caches them, and is then slow to release the RAM back to Stockfish, resulting in some swapping on Stockfish's move. The game was totally drawn anyway, and Stockfish was still getting to depths in the late 30s or better, so no harm done. Komodo's probe depth now set to 4 for the remainder of this match, increased for the second time. That is the equivalent of the setting of 2 that Stockfish is running. This should see the problem disappear completely.

I have not seen this issue before this match. The changes that were made in Komodo 1415 to increase the search depth must be responsible. So anyone running 6-men in engine matches, beware. This machine has 16GB of RAM, 32GB might solve the problem I guess but is not money that I want to spend.

This game has been aborted and will be replayed. Stockfish is heavily disadvantaged by this situation occurring.

Game 44 aborted with the same problem but in reverse. Stockfish spent 15 minutes on a move, tablebases were cached to a large extent, and then it was Komodo that was forced to suffer swapping on its move. Clearly you need 32GB of RAM to run 6-men reliably at very long time controls.

That is very interesting to note since it takes 32 GB of ram to generate the full 6 piece syzygy tables.

That is very different from reading from the ram taken from the SSD cartridge.

Are you also implying that one must allocate 32 GB of ram to each engine in order to properly read from the 6 pieces?

I am successfully able to have matches between said engines with different ram allocations apart from 32 GB.

However, I do possess 32 GB of ram hardware which may account for the performance difference.

I did some research on the price for memory sticks, and the average price newegg and amazon is $50-60 per 8 GB of ram. That is only $100-120 to upgrade from 16 GB to 32 GB. Why not spend the money? It worth for doubling your ram.

I'm not an expert with regards to this. Sorry. I was just making members aware of possible problems, that's all.

Please do not be sorry. I do not mean to be rude or combative. I am just concerned, because you make a valid statement which at this time makes for the possibility that many could be using their tables incorrectly. The unknown of this is what I fear.