#10 I don't think it's even a hardware problem. Seems more like a problem with downloading the engine and saving it in the browser for later use.
#1 #10 #11
Sorry, two different problems. Server side, it just takes longer for Stockfish 13 to run than previous versions. Client side, the first time it runs I think it downloads the neural net "weights file" as well as whatever it usually does. And then client side, it uses local cpu and memory as you set them up on the moves window menu.
Sorry, two different problems. Server side, it just takes longer for Stockfish 13 to run than previous versions. Client side, the first time it runs I think it downloads the neural net "weights file" as well as whatever it usually does. And then client side, it uses local cpu and memory as you set them up on the moves window menu.
lichess.org/blog/YDOKRxQAACgAREB3/stockfish-13-nnue-on-lichess
Reading this, another issue for server side it seems is that we have to wait until the server side database is "filled out" via the people running fishnet. That is, if a position in our game has been already analyzed by one of these fishnet users and updated, and verified, then the analysis would use that cache, and otherwise the server has to analyze that position. I'm thinking positions in the opening that would have previously used the cache. I have no idea how long that process of updating the server side is going to take. For instance, it means the people running fishnet have to update to fishnet 2.2.5.
Reading this, another issue for server side it seems is that we have to wait until the server side database is "filled out" via the people running fishnet. That is, if a position in our game has been already analyzed by one of these fishnet users and updated, and verified, then the analysis would use that cache, and otherwise the server has to analyze that position. I'm thinking positions in the opening that would have previously used the cache. I have no idea how long that process of updating the server side is going to take. For instance, it means the people running fishnet have to update to fishnet 2.2.5.
Don't use a stronger computer. I mean you can but it's not the solution for everything in life. If you have a computer made in 2001 then sure, buy a new one.
#10
There is an option in the moves window menu to turn off the NNUE. That will stop the download of the neural net weights file.
There is an option in the moves window menu to turn off the NNUE. That will stop the download of the neural net weights file.
#12 The problem here isn't with the server side analysis neither with stockfish using my hardware. "Client side, the first time it runs I think it downloads the neural net "weights file" as well as whatever it usually does." I think the problem is with this particular part instead of doing this procedure once or once in a while it does it for each and every game.
#15 Oh that worked actually. It changes to stockfish 11 and doesn't start downloading the file each and every time. Thank you.
#17 Great! I just tested it in Edge. Note: I had to reload the page to get toggle to work; then it switched to stockfish 11. Toggling it back, I had to reload the page again to get stockfish 13 again.
This topic has been archived and can no longer be replied to.