And here they are, played on a Nexus One using a random book opening play, one second-per-move, 32MB hash, and 8MB tablebases cache with the 3- and 4-piece Nalimov, Gaviota, Scorpio, Robbobases endgames on SD card (games available on request). It is good to see so many strong engines available for ARM-based Android devices now.
And here they are, played on a Nexus One using a random book opening play, one second-per-move, 32MB hash, and 8MB tablebases cache with the 3- and 4-piece Nalimov, Gaviota, Scorpio, Robbobases endgames on SD card (games available on request). It is good to see so many strong engines available for ARM-based Android devices now.
Out of curiosity, do you think with more games the performance will level out more? Also, do you think the TBs and types of TBs might be affecting the results of one engine over another?
"Tactics are the bricks and sticks that make up a game, but positional play is the architectural blueprint."
Albert Silver wrote:Out of curiosity, do you think with more games the performance will level out more? Also, do you think the TBs and types of TBs might be affecting the results of one engine over another?
More games are always better of course, but I have the impression that this list is pretty representative for the short time control. It would be interesting to see if longer time controls make a difference. Tablebases are actually not very relevant, since in this list only Ivanhoe supports robbototalbases.