[QUOTE=kriesel;531890]How to compile, and how to run, in one post.
[URL]https://www.mersenneforum.org/showpost.php?p=527930&postcount=7[/URL]
Since it uses git clone, and google drive, it gets the latest commit, and saves the compile results for efficiency.

There's a whole reference thread on colab in [URL]https://mersenneforum.org/showthread.php?t=24607[/URL][/QUOTE]

btw, I have tried to compile with this instructions but gpuOwl has some issue (some error) on running. So currently I'm using attached version from that post.

[QUOTE=kriesel;531890]How to compile, and how to run, in one post.
[URL]https://www.mersenneforum.org/showpost.php?p=527930&postcount=7[/URL]
Since it uses git clone, and google drive, it gets the latest commit, and saves the compile results for efficiency.

There's a whole reference thread on colab in [URL]https://mersenneforum.org/showthread.php?t=24607[/URL][/QUOTE]

Thanks it worked. I compiled the latest version running type 4 PRP test (f34ad18 from 20190627), but I found out it could not finish the savefile from the newest versions type 1 test.

Got a Tesla P4 today- ~700 ghz on mfaktc, but almost half the speed of a K80 in gpuowl..

Browsers
 

Had been using MS Edge as browser, for Colab access, until beginning ~Nov 29 I started getting the following any time gpu use was part of the runtime type:[CODE]Failed to execute cell. Could not send execute message to runtime: XhrHttpError: Request Failed, status=404, url=https://colab.research.google.com/tun/m/gpu-p100-s-3ltvic5j9g105/api/kernelspecs?authuser=0[/CODE]I could run mprime-only by specifying no GPU.

Switched to a current version of Firefox today on same system & task, and it launched ok, with GPU, first try, no error message.

[QUOTE=kracker;531974]Got a Tesla P4 today- ~700 ghz on mfaktc, but almost half the speed of a K80 in gpuowl..[/QUOTE]

Yeah. Much to my surprise I just got two. Strangely, one is getting ~700 GhD/D, while the second is getting ~1,800. Maybe we're sharing one (seriously).

[QUOTE=kriesel;532029]Had been using MS Edge as browser, for Colab access, until beginning ~Nov 29 I started getting the following any time gpu use was part of the runtime type:[CODE]Failed to execute cell. Could not send execute message to runtime: XhrHttpError: Request Failed, status=404, url=https://colab.research.google.com/tun/m/gpu-p100-s-3ltvic5j9g105/api/kernelspecs?authuser=0[/CODE]I could run mprime-only by specifying no GPU.

Switched to a current version of Firefox today on same system & task, and it launched ok, with GPU, first try, no error message.[/QUOTE]

I've never been able to get colab to work on edge since the beginning.

[QUOTE=chalsall;532032]Yeah. Much to my surprise I just got two. Strangely, one is getting ~700 GhD/D, while the second is getting ~1,800. Maybe we're sharing one (seriously).[/QUOTE]

That's odd... while that may be true the P4 is basically the little brother of the P100.

[code]
Tesla P4 vs Tesla P100 Theoretical Performance

Pixel Rate
71.30 GPixel/s vs 127.6 GPixel/s

Texture Rate
178.2 GTexel/s vs 297.7 GTexel/s

FP16 (half) performance
89.12 GFLOPS (1:64) vs 19.05 TFLOPS (2:1)

FP32 (float) performance
5.704 TFLOPS vs 9.526 TFLOPS

FP64 (double) performance
178.2 GFLOPS (1:32) vs 4.763 TFLOPS (1:2)
[/code]

[QUOTE=kracker;532033]I've never been able to get colab to work on edge since the beginning.[/QUOTE]What I described was on Windows 10 build 18362; using Google drive, and mprime/mfaktc combo; third code block of [URL]https://www.mersenneforum.org/showpost.php?p=528073&postcount=8[/URL]
In fairness to the Google Colab folks, it's been telling me all along that MS Edge is not a supported browser.

[QUOTE=kracker;532037]That's odd... while that may be true the P4 is basically the little brother of the P100.[/QUOTE]

I just double-checked; both are reporting T4s. I also got a P100 earlier -- it's getting ~1060 GHzD/D.

[QUOTE=chalsall;532041]I just double-checked; both are reporting T4s. I also got a P100 earlier -- it's getting ~1060 GHzD/D.[/QUOTE]


I got a "Tesla P4" today. I had not seen this before. It runs around 650 GHz-d/day.

Just got a one question survey while running colab saying "Would you be interested in a paid, premium version of colab?""