Life In 19x19

After a few searches, I now suspect I was connected to a P100, not A100. A huge difference of course.

I'd still guess that P100 supports CUDA though.

wineandgolover wrote:After a few searches, I now suspect I was connected to a P100, not A100. A huge difference of course.

I'd still guess that P100 supports CUDA though.

Again to answer my own question.

I was so excited to contribute to KataGo that I used the script a lot and Google put the breaks on my use of Colab. (Don't run it all the time, if you want to use it for free, folks)

I've upgraded to Colab Pro, because I'm still excited to help. And paying $10/month for the duration of the project is a hell of a lot cheaper than buying and running a powerful GPU.

Since upgrading, I've 100% been assigned P100 GPU, which I believe is supposed to be better than the T4. Perhaps that is so, but not for this job, with this Colab script.

After several tests on the P100, in which I forced it to use CUDA, it worked, but was significantly slower than OpenCL. So the script is right to use OpenCL.

Unfortunately, the P100 running OpenCL is also slower than the T4 GPU running CUDA. I am currently getting around 340 nnevals/second with 8 simultaneous games, and 385 nnevals/second with 16. (versus 380 and 525 nnevals/sec for the T4 running CUDA)

Unfortunately, with Colab, I believe you have to take the GPU you are given. And because I am a good paying customer, I consistently get the "superior" P100.

The good news is that I seem to be able to run scripts in two browser windows, and it disconnects far less often. And so far, Google hasn't told me to back off.

I still strongly recommend every go player try it. It's kind of like the SETI project for go players, except that Google is running the GPU's, so all you need is a simple browser tab. It's also easy, I'm running the script from the first post, just with my user name and password, no other changes. And it's free for those of you less obsessive than me.

If you don't want to train katago, but just play rating games, would this work?
https://github.com/portkata/KataGo/blob ... ames.ipynb
probably have to replace cuda with auto.

Notebook image's been updated to use Katago v1.8.1 today.

KataGo v1.8.2 engines have released today.

So I've updated colab image to use new KataGo version.

You may need to copy colab image again so far.

Thanks.

Is anyone else getting the message that the cannot connect to the GPU backend due to high usage rates? I’ve only been running a single instance at a time, but have been blocked for the last three days.

The free version is still working for me, but I haven't been running it lately. You are on the paid version, aren't you? Looks like their on to you. Better stop your subscription!

Edit: I posted too soon! My run was terminated without completing any games. When I retry I now see "You cannot currently connect to a GPU due to usage limits in Colab."

Same issue here. Even the Colab Pro version does not work now... My training was stopped just after first game completed and uploaded.