That's really weird - weiss definitely does not do this on my machine. What OS are you on?Gabor Szots wrote: ↑Sat Nov 23, 2019 4:24 pmYes, although I do not know if it was a TB position because there were still many pieces (I think 10) on the board.Terje wrote: ↑Sat Nov 23, 2019 4:20 pmIs that playing a lot of moves after reaching a tablebase position or something? Locally I test with 1024MB hash, and have only ever seen it sit around 1053MB total in task manager.Gabor Szots wrote: ↑Sat Nov 23, 2019 4:01 pm I allocate 256 MB hash for the engine but by the end of the game its memory allocation reaches almost 2 GB. Probably because of syzygy bases but I am afraid my 8 GB RAM won't like it.
Engine release: weiss
Moderators: hgm, Rebel, chrisw
-
- Posts: 347
- Joined: Tue Nov 19, 2019 4:34 am
- Location: https://github.com/TerjeKir/weiss
- Full name: Terje Kirstihagen
Re: Engine release: weiss
-
- Posts: 1364
- Joined: Sat Jul 21, 2018 7:43 am
- Location: Szentendre, Hungary
- Full name: Gabor Szots
Re: Engine release: weiss
64-bit W10.Terje wrote: ↑Sat Nov 23, 2019 4:33 pmThat's really weird - weiss definitely does not do this on my machine. What OS are you on?Gabor Szots wrote: ↑Sat Nov 23, 2019 4:24 pmYes, although I do not know if it was a TB position because there were still many pieces (I think 10) on the board.Terje wrote: ↑Sat Nov 23, 2019 4:20 pmIs that playing a lot of moves after reaching a tablebase position or something? Locally I test with 1024MB hash, and have only ever seen it sit around 1053MB total in task manager.Gabor Szots wrote: ↑Sat Nov 23, 2019 4:01 pm I allocate 256 MB hash for the engine but by the end of the game its memory allocation reaches almost 2 GB. Probably because of syzygy bases but I am afraid my 8 GB RAM won't like it.
Gabor Szots
CCRL testing group
CCRL testing group
-
- Posts: 347
- Joined: Tue Nov 19, 2019 4:34 am
- Location: https://github.com/TerjeKir/weiss
- Full name: Terje Kirstihagen
Re: Engine release: weiss
Hmm, what time control?Gabor Szots wrote: ↑Sat Nov 23, 2019 4:35 pm64-bit W10.Terje wrote: ↑Sat Nov 23, 2019 4:33 pmThat's really weird - weiss definitely does not do this on my machine. What OS are you on?Gabor Szots wrote: ↑Sat Nov 23, 2019 4:24 pmYes, although I do not know if it was a TB position because there were still many pieces (I think 10) on the board.Terje wrote: ↑Sat Nov 23, 2019 4:20 pmIs that playing a lot of moves after reaching a tablebase position or something? Locally I test with 1024MB hash, and have only ever seen it sit around 1053MB total in task manager.Gabor Szots wrote: ↑Sat Nov 23, 2019 4:01 pm I allocate 256 MB hash for the engine but by the end of the game its memory allocation reaches almost 2 GB. Probably because of syzygy bases but I am afraid my 8 GB RAM won't like it.
Tried a game without pext, 256MB hash, 2 seconds per move, even after reaching a position with 4 pieces and getting 200k tbhits the memory usage was barely higher than at the start (264 -> 268).
-
- Posts: 1364
- Joined: Sat Jul 21, 2018 7:43 am
- Location: Szentendre, Hungary
- Full name: Gabor Szots
-
- Posts: 347
- Joined: Tue Nov 19, 2019 4:34 am
- Location: https://github.com/TerjeKir/weiss
- Full name: Terje Kirstihagen
Re: Engine release: weiss
Even with the compile you provided I can't seem to replicate the issue. At most it rose to 270MB here, while getting 500k+ tbhits for many moves. Could it matter what the tablebases are stored on? Could you try running again without tablebases to see if it happens without them?
-
- Posts: 1364
- Joined: Sat Jul 21, 2018 7:43 am
- Location: Szentendre, Hungary
- Full name: Gabor Szots
Re: Engine release: weiss
I did not compile anything, must have been someone else.Terje wrote: ↑Sat Nov 23, 2019 5:06 pmEven with the compile you provided I can't seem to replicate the issue. At most it rose to 270MB here, while getting 500k+ tbhits for many moves. Could it matter what the tablebases are stored on? Could you try running again without tablebases to see if it happens without them?
I am in the middle of a tournament and can't change engine parameters permanently without corrupting the result. However, for a couple of games maybe it won't hurt so I am going to do it.
I am sure it's the syzygy, I have seen this with other engines too.
Gabor Szots
CCRL testing group
CCRL testing group
-
- Posts: 347
- Joined: Tue Nov 19, 2019 4:34 am
- Location: https://github.com/TerjeKir/weiss
- Full name: Terje Kirstihagen
Re: Engine release: weiss
Oh oops. Ok, I see. Thanks for helping!Gabor Szots wrote: ↑Sat Nov 23, 2019 5:13 pm I did not compile anything, must have been someone else.
I am in the middle of a tournament and can't change engine parameters permanently without corrupting the result. However, for a couple of games maybe it won't hurt so I am going to do it.
I am sure it's the syzygy, I have seen this with other engines too.
-
- Posts: 1364
- Joined: Sat Jul 21, 2018 7:43 am
- Location: Szentendre, Hungary
- Full name: Gabor Szots
Re: Engine release: weiss
I have just followed one 11-piece ending until the conclusion without syzygy in use. The memory allocation remained at 259 MB throughout. Q.E.D.
Gabor Szots
CCRL testing group
CCRL testing group
-
- Posts: 347
- Joined: Tue Nov 19, 2019 4:34 am
- Location: https://github.com/TerjeKir/weiss
- Full name: Terje Kirstihagen
Re: Engine release: weiss
Ok, thanks for confirming.Gabor Szots wrote: ↑Sat Nov 23, 2019 5:38 pm I have just followed one 11-piece ending until the conclusion without syzygy in use. The memory allocation remained at 259 MB throughout. Q.E.D.