Google Diet Colab Notebook - Page 112

lycorn · 2022-06-15, 07:04

It ran for 5h 31m.
Just started another run from a different account. Got a T4 as well. As I´m leaving home now, I won´t be around to click and extend the running time, so I guess it will stop after a bit more than 3 hours.
It´s weird that Colab is currently being more liberal on GPUs than on CPUs, but we should already be used to their oddities

.

kriesel · 2022-06-15, 13:28

last evening, same accounts as https://mersenneforum.org/showpost.p...postcount=1218
hh:mm, resolution ~3 or 4 minutes; scripts similar to https://www.mersenneforum.org/showthread.php?t=24839

mprime+mfaktc: 3:32; 3:45; 3:31
mprime+gpuowl: 1:58; 3:54
mprime only: no samples

That is quite different from the previous run cycle, in a good way. Maybe Google just had exceptionally high demand for paying compute for a while and was promptly kicking out us freeloaders during peak paid usage.

slandrum · 2022-06-15, 13:29

All my CPU only sessions are running. They've passed the 6 hours 40 minutes mark, and no recaptcha popups. Usually at 6:01 to 6:10 there's a recaptcha, and if it's not responded to in time the sessions are killed at around 6:40.

chalsall · 2022-06-16, 20:50

Quote:

Originally Posted by slandrum

All my CPU only sessions are running. They've passed the 6 hours 40 minutes mark, and no recaptcha popups.

Yup. I can confirm the usage patterns are back to nominal (at least for the mfaktc/mprime and mprime runs).

Thanks, Colab / Google. You had us a little worried there for a bit...

2022-06-15, 13:28	#1223
kriesel "TF79LL86GIMPS96gpu17" Mar 2017 US midwest 2×3×7×157 Posts	last evening, same accounts as https://mersenneforum.org/showpost.p...postcount=1218 hh:mm, resolution ~3 or 4 minutes; scripts similar to https://www.mersenneforum.org/showthread.php?t=24839 mprime+mfaktc: 3:32; 3:45; 3:31 mprime+gpuowl: 1:58; 3:54 mprime only: no samples That is quite different from the previous run cycle, in a good way. Maybe Google just had exceptionally high demand for paying compute for a while and was promptly kicking out us freeloaders during peak paid usage. Last fiddled with by kriesel on 2022-06-15 at 13:49

2022-06-15, 13:29	#1224
slandrum Jan 2021 California 2²×107 Posts	All my CPU only sessions are running. They've passed the 6 hours 40 minutes mark, and no recaptcha popups. Usually at 6:01 to 6:10 there's a recaptcha, and if it's not responded to in time the sessions are killed at around 6:40. Last fiddled with by slandrum on 2022-06-15 at 13:43

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

2022-06-15, 07:04	#1222
lycorn "GIMFS" Sep 2002 Oeiras, Portugal 2²×3²×43 Posts	It ran for 5h 31m. Just started another run from a different account. Got a T4 as well. As I´m leaving home now, I won´t be around to click and extend the running time, so I guess it will stop after a bit more than 3 hours. It´s weird that Colab is currently being more liberal on GPUs than on CPUs, but we should already be used to their oddities .