ThatsIt wrote:Another problem: too many time losses @ level xy move in zz time repeated !
I got 8 within only 200 games.
Best wishes,
G.S.
I've alerted Fabio to all the concerns in this thread.
From Youri:
I added option "SyzygyPath". It does the same thing as "NalimovPath". The engine only supports syzygy EGTBs, but their path can be passed to engine under either of those two options. If there are no syzygy files in that path, then syzygy EGTBs will not be used.
Time losses: i did not see them in my testing. I can only hope that they are caused by small excess of time over allowed limit, so i increased the time margin in my engine - hopefully this will fix the problem. If the problem persists, i would probably need to see a log of all traffic between GUI and engine.
ThatsIt wrote:I added option "SyzygyPath". It does the same thing as "NalimovPath". The engine only supports syzygy EGTBs, but their path can be passed to engine under either of those two options. If there are no syzygy files in that path, then syzygy EGTBs will not be used.
...
Youri.
I'd remove that Nalimovpath option. Why mislead people?
ymatioun wrote:OK, i will remove "Nalimov" option right away - updated files will be on my site within an hour.
Youri.
Thanks for giving us Fizbo, Youri!
I'm noticing that enabling Syzygy usage causes Fizbo to gobble up more and more RAM. The amount of RAM used keeps increasing as Fizbo is calculating.
There is also a big drop in nps and depth in the endgames.
The first released binary of Fizbo 1.5 did not have these issues, but, of course, could not access the Syzygy tablebases, as it was hardcoded to look for them on the H: drive.
I'm wondering if others are witnessing the same behavior.
I just ran a few games with the latest file (to make sure i did not mess up compile) and i don't see any memory increase. Normally i run 1,000 games in testing, and that does not lead no any memory increase.
Slow search with EGTB turned on: i don't see it either. I just ran search on a simple position (8/4k3/3pp3/8/8/3PP3/4K3/8 w - - 0 1): with SYZYGY, i see depth 43 (and stop) after 0.1 sec and 326,448 nodes. Without EGTB i stop at depth 43 after 12 seconds and 48 Million nodes.
But i think EGTB files have to be on a media with low latency - SSD or similar. If you have them on a hard drive, they may significantly reduce performance. Other than this, i have no ides why you see these problems. All i can say is that i don't see anything like that.
ymatioun wrote:I just ran a few games with the latest file (to make sure i did not mess up compile) and i don't see any memory increase. Normally i run 1,000 games in testing, and that does not lead no any memory increase.
Slow search with EGTB turned on: i don't see it either. I just ran search on a simple position (8/4k3/3pp3/8/8/3PP3/4K3/8 w - - 0 1): with SYZYGY, i see depth 43 (and stop) after 0.1 sec and 326,448 nodes. Without EGTB i stop at depth 43 after 12 seconds and 48 Million nodes.
But i think EGTB files have to be on a media with low latency - SSD or similar. If you have them on a hard drive, they may significantly reduce performance. Other than this, i have no ides why you see these problems. All i can say is that i don't see anything like that.
Youri.
They are 5-man syzygy tbs on a regular HD, but these are not supposed to impact performance as much as 6-man syzygy (which need SSD), unless I'm mistaken.
Fizbo uses EGTBs two ways: W/L/D tables are used inside search. So they get accessed as soon as number on pieces on board drops to 5. This part requires tables to be on SSD, because they are accessed a lot.
Second way is using depth-to-zero tables when there are 5 or fewer piece on the board. This piece would work from hard drive.
Unfortunately, currently i have no way to only do the second part without the first one. So if files are not on SSD then endgame search will be very slow.
