Google Diet Colab Notebook - Page 59

Lorenzo · 2019-12-03, 11:36

Quote:

Originally Posted by kriesel

How to compile, and how to run, in one post.
https://www.mersenneforum.org/showpo...30&postcount=7
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 https://mersenneforum.org/showthread.php?t=24607

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.

ATH · 2019-12-03, 14:10

Quote:

Originally Posted by kriesel

How to compile, and how to run, in one post.
https://www.mersenneforum.org/showpo...30&postcount=7
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 https://mersenneforum.org/showthread.php?t=24607

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.

kracker · 2019-12-04, 05:17

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

kriesel · 2019-12-04, 19:42

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

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.

chalsall · 2019-12-04, 19:54

Quote:

Originally Posted by kracker

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

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).

kracker · 2019-12-04, 19:58

Quote:

Originally Posted by kriesel

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

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.

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

kracker · 2019-12-04, 20:16

Quote:

Originally Posted by chalsall

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).

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)

kriesel · 2019-12-04, 20:19

Quote:

Originally Posted by kracker

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

What I described was on Windows 10 build 18362; using Google drive, and mprime/mfaktc combo; third code block of https://www.mersenneforum.org/showpo...73&postcount=8
In fairness to the Google Colab folks, it's been telling me all along that MS Edge is not a supported browser.

chalsall · 2019-12-04, 20:24

Quote:

Originally Posted by kracker

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

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

storm5510 · 2019-12-05, 01:30

Quote:

Originally Posted by chalsall

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

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

kracker · 2019-12-05, 13:33

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

2019-12-04, 19:42	#642
kriesel "TF79LL86GIMPS96gpu17" Mar 2017 US midwest 5,437 Posts	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 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.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Alternatives to Google Colab	kriesel	Cloud Computing	11	2020-01-14 18:45
Notebook	enzocreti	enzocreti	0	2019-02-15 08:20
Computer Diet causes Machine Check Exception -- need heuristics help	Christenson	Hardware	32	2011-12-25 08:17
Computer diet - Need help	garo	Hardware	41	2011-10-06 04:06
Workunit diet ?	dsouza123	NFSNET Discussion	5	2004-02-27 00:42

2019-12-04, 05:17	#641
kracker "Mr. Meeseeks" Jan 2012 California, USA 878₁₆ Posts	Got a Tesla P4 today- ~700 ghz on mfaktc, but almost half the speed of a K80 in gpuowl..

2019-12-05, 13:33	#649
kracker "Mr. Meeseeks" Jan 2012 California, USA 2168₁₀ Posts	Just got a one question survey while running colab saying "Would you be interested in a paid, premium version of colab?""