So when I have Lichess computer analysis running, it lets me select how much ram to use, but the slider maxes out at 32meg which is really tiny when trying to do a deep analysis with lots of CPUs. And less than 1/1000th of my computer's memory so it's a rather unreasonable limit as far as I can tell. Could this be boosted a lot?
So when I have Lichess computer analysis running, it lets me select how much ram to use, but the slider maxes out at 32meg which is really tiny when trying to do a deep analysis with lots of CPUs. And less than 1/1000th of my computer's memory so it's a rather unreasonable limit as far as I can tell. Could this be boosted a lot?
Are you by chance using Firefox? I think Chrome allows for 1GB but Firefox only has support for 32MB, although it could be possible to increase this. I found this previous forum thread which might be a good place to start: https://lichess.org/forum/off-topic-discussion/is-there-a-way-to-increase-stockfishs-memory-limit-past-32-mb-on-firefox
Are you by chance using Firefox? I think Chrome allows for 1GB but Firefox only has support for 32MB, although it could be possible to increase this. I found this previous forum thread which might be a good place to start: https://lichess.org/forum/off-topic-discussion/is-there-a-way-to-increase-stockfishs-memory-limit-past-32-mb-on-firefox
If you want to run the newest version of stockfish and control all the parameters the easiest thing to do is to download it from https://stockfishchess.org/
I use 8gb of memory when I run it locally.
If you want to run the newest version of stockfish and control all the parameters the easiest thing to do is to download it from https://stockfishchess.org/
I use 8gb of memory when I run it locally.
The issue is that Firefox doesn't actually tell websites how much memory your device supports so Lichess has to guess and uses a conservative low value.
Chrome and the browsers based on it support the navigator.deviceMemory API which allows Lichess to at least roughly find out how much memory is actually available.
The issue is that Firefox doesn't actually tell websites how much memory your device supports so Lichess has to guess and uses a conservative low value.
Chrome and the browsers based on it support the navigator.deviceMemory API which allows Lichess to at least roughly find out how much memory is actually available.