I'm getting maybe 10 or 15 minutes with Colab before having to reset
 

Lately as I'm sure with most everybody else I'm getting maybe 10 or 15 minutes with Colab before having to reset. I'm running 1 key on 2 different accounts. Most of the time I only get P-1 at around 500 sec, Today this is what I was getting. :unsure: What the heck did I miss? LOL

[QUOTE=mrk74;581165]Today this is what I was getting. :unsure: What the heck did I miss? LOL[/QUOTE]

Yeah... The Colab Gods are acting mysteriously lately. Several of my instances are getting 6+ hours at a time; often a good twelve or so of runtime a day!

Don't know how long it will last for, but it's nice getting the compute again. :smile:

[QUOTE=chalsall;581166]Yeah... The Colab Gods are acting mysteriously lately. Several of my instances are getting 6+ hours at a time; often a good twelve or so of runtime a day!

Don't know how long it will last for, but it's nice getting the compute again. :smile:[/QUOTE]

I'm probably jinxing it but this run has run for a couple hours at this point. I'll take what I can get but I haven't getting any TF's in quite a while.

[QUOTE=chalsall;581166]Yeah... The Colab Gods are acting mysteriously lately. Several of my instances are getting 6+ hours at a time; often a good twelve or so of runtime a day!
[/QUOTE]
Same here. 3 data points are a line.

My instances stopped showing as running in the browser the last ~1 week, but they are actually still running, very weird.

[QUOTE=ATH;581175]My instances stopped showing as running in the browser the last ~1 week, but they are actually still running, very weird.[/QUOTE]
Just try to reattach, but don't click the stop/start button.

[QUOTE=Uncwilly;581178]Just try to reattach, but don't click the stop/start button.[/QUOTE]

Yeah, that worked. But I never had to do that until about 1 week ago. It used to continue showing the spinning start/stop button until the session ended.
Maybe I can close the browser now when it does that disconnect but still running.

[QUOTE=ATH;581181]Maybe I can close the browser now when it does that disconnect but still running.[/QUOTE]Sometimes that works. I have transferred sessions between home and work like that. Other times it has died. Other times the original session spins away and I get a second session running concurrently.

Run only one instance at one account at the same time, preferably PRP or LL DC. I use 3 google accounts in a row. I get a 3 -5 hour runtime granted, and that after a year. You may have to wait 3-5 hours before you can count on the next account. Believe me this strategy is not the worst!

Run one instance PER Colab free account/email address, simultaneously. I reliably get all 6 accounts going, multiple times daily. The session following a GPU-too session ~4 hours runtime is usually a CPU-only session ~7 hours runtime. If I run each account 2-3 times daily, I get those durations. More frequently, and I may see some 1.5 hour durations. There are users running more accounts, much more.

The new twist is the "Failed to execute cell" etc error message, described near the end of [URL]https://www.mersenneforum.org/showpost.php?p=527909&postcount=2[/URL]. Retry usually clears it up quickly.

Haven't been able to get P100 for the last 3 days

I'm not running GPUto72, but I've been playing around with Colab accounts for a little bit (a few months).

For each account, I can run a CPU only instance and a GPU instance. I can run the CPU instance around the clock, as soon as it ends I can restart it immediately. At 6 hours + a random amount of minutes between 2 and 45 it will put up a reCaptcha dialog to verify that I'm still there. Lately it will frequently (maybe 1/5 of the time) also have one of the "are you really a human" puzzles where you have to pick a set of pictures. If I respond to this in time, the session will last approximately 12 hours (total). If I don't respond it will terminate my session some time before the 7 hour mark. I can immediately restart the session though, right after it's been terminated (I'll get a different machine).

While having the CPU session (nearly) continuously running I can run a GPU session. The time I get on the GPU varies from 2 hours (actually the shortest was 1 hour 15 minutes) to 14 hours. If the session lasts longer than 3 hours, it will pop up the reCaptcha within 2 minutes of the session going over 3 hours. The GPU sessions lately have been kicking me off at under 3 hours (2:25 to 2:50 is what I've been getting for about a week) but the week prior to that I was averaging about 4 hours per session, and the week before that just over 3 hours/session. One of my accounts has now gone 5 days w/o letting me get a GPU session at all (this is a new behavior). On all the other accounts it's letting me get 1 GPU session in a 24 hour period.

These are all free accounts.

I usually get a T4 for the GPU session. I sometimes get a K80, and rarely a P100. If I get a P4 (even rarer than the P100) I kill the session, and start a new one to get a different GPU - for what I've been running the P4 gives the worst results - 25% slower than a T4. With the K80 I get comparable results to the T4 - maybe 5-10% faster on average, but each instance has different timing and the best T4 timings are better than the worst K80 timings.. With the P100 I get 4.5x faster results than with the T4 on average.

I'm considering switching from P-1 to TF if all I can get is T4's.

I just need build for mfaktc for colab,

Actually my preference would be to have a script that asks for a GPU then
IF: T4 run mfaktc
IF: P100 run GPUOwl P-1
ELSE: try again

[QUOTE=petrw1;581203]Haven't been able to get P100 for the last 3 days[/QUOTE]
Me too, but was be able to get more Tesla K-80 runtimes as usual.

[QUOTE=petrw1;581207]I'm considering switching from P-1 to TF if all I can get is T4's.

I just need build for mfaktc for colab,

Actually my preference would be to have a script that asks for a GPU then
IF: T4 run mfaktc
IF: P100 run GPUOwl P-1
ELSE: try again[/QUOTE]Have a look at the script at [URL]https://www.mersenneforum.org/showpost.php?p=537155&postcount=16[/URL] and adapt it to do what you want. Mfaktc at [URL]https://www.mersenneforum.org/showpost.php?p=525399&postcount=25[/URL] or [url]https://download.mersenne.ca/mfaktc/mfaktc-0.21[/url]

[QUOTE=petrw1;581207]Actually my preference would be to have a script that asks for a GPU then
IF: T4 run mfaktc
IF: P100 run GPUOwl P-1
ELSE: try again[/QUOTE]
And what about the K-80? it is definitely good for double checks, then probably also for P-1.
[CODE]2021-06-17 12:21:40 gpuowl v6.11-380-g79ea0cc
2021-06-17 12:21:40 Note: not found 'config.txt'
2021-06-17 12:21:41 config: -carry short -use CARRY32,ORIG_SLOWTRIG,IN_WG=128,IN_SIZEX=16,IN_SPACING=4,OUT_WG=128,OUT_SIZEX=16,OUT_SPACING=4 -nospin -block 100 -maxAlloc 10000 -B1 750000 -rB2 20
2021-06-17 12:21:41 device 0, unique id ''
2021-06-17 12:21:41 Tesla K80-0 57641347 FFT: 3M 1K:6:256 (18.32 bpw)
2021-06-17 12:21:41 Tesla K80-0 Expected maximum carry32: 3ED80000
2021-06-17 12:21:42 Tesla K80-0 OpenCL args "-DEXP=57641347u -DWIDTH=1024u -DSMALL_HEIGHT=256u -DMIDDLE=6u -DPM1=0 -DWEIGHT_STEP_MINUS_1=0x1.32332220cd858p-1 -DIWEIGHT_STEP_MINUS_1=-0x1.7f37b40db846ep-2 -DCARRY32=1 -DIN_SIZEX=16 -DIN_SPACING=4 -DIN_WG=128 -DORIG_SLOWTRIG=1 -DOUT_SIZEX=16 -DOUT_SPACING=4 -DOUT_WG=128 -cl-unsafe-math-optimizations -cl-std=CL2.0 -cl-finite-math-only "
2021-06-17 12:21:45 Tesla K80-0

2021-06-17 12:21:45 Tesla K80-0 OpenCL compilation in 3.02 s
2021-06-17 12:21:46 Tesla K80-0 57641347 LL 39500000 loaded: 4d3e186ee9074c1e
2021-06-17 12:25:12 Tesla K80-0 57641347 LL 39600000 68.70%; 2055 us/it; ETA 0d 10:18; 8cbc7bdc53b01d7b
2021-06-17 12:28:38 Tesla K80-0 57641347 LL 39700000 68.87%; 2061 us/it; ETA 0d 10:16; 9dad6557559689e3
2021-06-17 12:32:04 Tesla K80-0 57641347 LL 39800000 69.05%; 2061 us/it; ETA 0d 10:13; 3e7b66ea3779bd0b
2021-06-17 12:35:30 Tesla K80-0 57641347 LL 39900000 69.22%; 2061 us/it; ETA 0d 10:09; 0bc408c38dce350a
2021-06-17 12:38:56 Tesla K80-0 57641347 LL 40000000 69.39%; 2061 us/it; ETA 0d 10:06; 31799786a944acae
2021-06-17 12:42:22 Tesla K80-0 57641347 LL 40100000 69.57%; 2061 us/it; ETA 0d 10:03; 40a53371c5d36a44
2021-06-17 12:42:22 Tesla K80-0 57641347 OK 40000000 (jacobi == -1)
2021-06-17 12:45:48 Tesla K80-0 57641347 LL 40200000 69.74%; 2062 us/it; ETA 0d 09:59; 64bc9996665bee17
2021-06-17 12:49:14 Tesla K80-0 57641347 LL 40300000 69.92%; 2061 us/it; ETA 0d 09:56; 5338e9b91692daa3[/CODE]

[QUOTE=moebius;581230]And what about the K-80? it is definitely good for double checks, then probably also for P-1.
[/QUOTE]

Using0 GPUOwl it is 4 times slower than a P100 for P-1

[QUOTE=kriesel;581214]Have a look at the script at [URL]https://www.mersenneforum.org/showpost.php?p=537155&postcount=16[/URL] and adapt it to do what you want. Mfaktc at [URL]https://www.mersenneforum.org/showpost.php?p=525399&postcount=25[/URL] or [url]https://download.mersenne.ca/mfaktc/mfaktc-0.21[/url][/QUOTE]

Thanks

[QUOTE=moebius;581230]And what about the K-80? it is definitely good for double checks, then probably also for P-1.[/QUOTE]
You don't get a full K80. K80 is a dual-chip card, and you only get half of it. The rest, as Wayne said.

[QUOTE=LaurV;581252]You don't get a full K80. K80 is a dual-chip card, and you only get half of it. The rest, as Wayne said.[/QUOTE]
gpuOwl is good, but I don't think that a gpuOWL_instance can use both gpus of the Tesla K-80 at the same time. The values I have are only for one instance of gpuOWl.

[QUOTE=petrw1;581236]Using0 GPUOwl it is 4 times slower than a P100 for P-1[/QUOTE]
Yes, a K-80 instance is only slightly slower in the LL DC range than a 8-core AMD Ryzen 3700X.

[QUOTE=moebius;581272]gpuOwl is good, but I don't think that a gpuOWL_instance can use both gpus of the Tesla K-80 at the same time. The values I have are only for one instance of gpuOWl.[/QUOTE]Gpuowl can't use more hardware than is present.
The K80 is a dual-GPU card. The Colab free sessions offer a CPU core (often with HT) and sometimes a single GPU (such as one GPU, 12GB GPU ram, half the K80 card).