We benchmarked a full game tree search and found:
Platform, Browser | M 0.9.2 | C 0.9.2 |
---|---|---|
Windows 10, Chrome | 312 | 276 |
Apple MacBook, Safari Prev | 287 | 269 |
Android Tablet, Chrome | 1'614 | 1'422 |
Apple iPad, Safari | N/A | 312 |
We used laptops and devices not older than 5 years. We could not make the module version of Dogelog player execute on all platform and browser combination. The offending language construct was import(), which was not available on an iPad, and worked only on a MacBook after installing Safari technology preview.
We also measured canned Dogelog, which does not require modules. Interestingly canned Dogelog is faster, which might have to do that modules do have different JavaScript execution schemas. Most likely, the gap will go away in the future. Interestingly the little iPad was almost beating a laptop in speed.
Because there will be already a move when the game search kicks in, the game search will need 2-4 times less time than a full game search tree from the beginning. This means that on most platform and browser combinations the response time will be below 100ms, otherwise the end-user might get frustrated, annoyed or even angry.
Here is a screenshot where the computer wins: