Closed scaljeri closed 5 years ago
This is expected behavior. Weights that have more blocks and filters take more time to compute. Running large weight files on CPU is not advised due to how poorly CPUs are at inference compared to GPUs (particularly Nvidia GPUs). If you wish to run larger weight files, you need better hardware and/or need to wait longer.
Thanks for the quick reply. Thats to bad for me, my system doesn't support GPU stuff.
I have two weight files, one with a size of 6MB and the other 45MB (files is listed here). The problem is that when I start to compute a move, it takes too much time, especially when I use the larger weight file. Below I start lc0 with the larger weight file
and compute a move
I get
This takes approximately 3 seconds. Now, when I do this computation again, it seems to take even more time
info depth 2 seldepth 2 time 4957 nodes 3 score cp 44 hashfull 0 nps 0 tbhits 0 pv c1d2 a7a6 bestmove c1d2 ponder a7a6
If I use the smaller weight file it takes about 1 seconds.
In my case I would like to use lc0 to play 1 minute games, so these delays are way to huge. For example, I'm also using Stockfish which doesn't have these issues.
I would like to play 1 minutes games with lc0, but with these slow computation times it is not possible. Is there a way to speed things up?
If you want to see it yourself, I've published
lc0
on my DockerHub, so you can try it out yourselfUsing the smaller weight file:
And to run the one using the bigger weight file
After you have entered one of the above commands you can simply past the positions into the terminal and see the result
Also, to get an idea of how I've build lco, here is my dockerfile
From jeanluca/base:latest