Sure, this is also true that many testers are doing their best Where they produce a lot of useful data.BIG thanks to all. Now one of the main questions is that (matches on same hardware): - What is the right and best way of testing the chess engines? And according to my experience, There is no any perfect GUI or Engine or Opening Book etc. 18 simultaneously matches Btw, Cutechess crashed with Concurrent games: 60 (1 Thread, HT ON) 36 simultaneously matches= 1 Core / Ponder OFF In case of 1 Core but with Ponder ON: max. As you may know, Cutechess GUI has a simultaneously option: Concurrent games' (playing automatically matches in same time) So it's not required to run several GUIs (in same time) Note: Concurrent's option can be used for machines with many CPUs For example, my 2x 2686 has 36 real cores (Hyper-Threading OFF): So I can run max.

And all the games are played by same copy/folder of engines. This time, Only two Top engines are tested under Arena 3.5.1 and Cutechess 1.2.0 The target is to see the influence of running simultaneously matches! One of the main differences is that (between both GUI testings), Several GUIs were running (during Arena's simultaneously matches) E.g all of the engine games are played by separate folder of engines I mean, for each Arena GUI: I installed a separate copy of engines Where via Cutechess: only one GUI was running.

I am pleased to announce that, I organized another new GUI/Engine testings!įirst of all, let Me start please with Any engine's rating depends on our used conditions: - Hardware speed - Opening Book/Suite - MP or 1 Core - Ponder ON/OFF - Time Control - Hyper-Threading ON/OFF - Hash-Table Size - GUI - Tester/TD And etc.

Testing stockfish chess