I am trying to use the web tablebase API to check 7-piece endgames by sending a GET Request to the URL
http://tablebase.lichess.ovh/standard?fen= followed by the FEN.
I have found in my tests that a GET seems to be failing after 130 accesses or so (from a script, so very rapid). On the other hand, it is very possible there is a bug in my script that is causing this issue.
Does the web tablebase API throttle or fail when it detects rapid accesses; and if so what parameters can I use to get around this? I would like to check quite a lot of positions, 100s of thousands.
I am trying to use the web tablebase API to check 7-piece endgames by sending a GET Request to the URL
http://tablebase.lichess.ovh/standard?fen= followed by the FEN.
I have found in my tests that a GET seems to be failing after 130 accesses or so (from a script, so very rapid). On the other hand, it is very possible there is a bug in my script that is causing this issue.
Does the web tablebase API throttle or fail when it detects rapid accesses; and if so what parameters can I use to get around this? I would like to check quite a lot of positions, 100s of thousands.
Yes. The usual rate limiting rules for the Lichess API apply: https://lichess.org/api#section/Introduction/Rate-limiting
The disks can only handle so much througput, and it's supposed to a service for many users, so please do not try to work around it. If you really need that many requests you can download (https://syzygy-tables.info/#download) the tables and probe them locally. Towards the end, https://lichess.org/blog/W3WeMyQAACQAdfAL/7-piece-syzygy-tablebases-are-complete mentions some libaries that can be used for local probing.
Yes. The usual rate limiting rules for the Lichess API apply: https://lichess.org/api#section/Introduction/Rate-limiting
The disks can only handle so much througput, and it's supposed to a service for many users, so please do not try to work around it. If you really need that many requests you can download (https://syzygy-tables.info/#download) the tables and probe them locally. Towards the end, https://lichess.org/blog/W3WeMyQAACQAdfAL/7-piece-syzygy-tablebases-are-complete mentions some libaries that can be used for local probing.
@revoof Thank you for the information, it is very helpful. I can easily rate limit my own requests to one every few seconds, I am checking a single database, which, once checked, will be finished. Perhaps I can reduce the position count as well.
The link you provided to the download information lists 3 URLs for 7-piece tablebases, but the ipfs.syzygy-tables.info one appears to be down, leaving only 2 left, both of which are in the EU. Downloading 16 TB to the US from there seems like a difficult task although I have not measured the bandwidth recently. If you have other alternatives, pay or free, for acquiring the 16 TB database, I would like it locally for other projects.
@revoof Thank you for the information, it is very helpful. I can easily rate limit my own requests to one every few seconds, I am checking a single database, which, once checked, will be finished. Perhaps I can reduce the position count as well.
The link you provided to the download information lists 3 URLs for 7-piece tablebases, but the ipfs.syzygy-tables.info one appears to be down, leaving only 2 left, both of which are in the EU. Downloading 16 TB to the US from there seems like a difficult task although I have not measured the bandwidth recently. If you have other alternatives, pay or free, for acquiring the 16 TB database, I would like it locally for other projects.