Google Diet Colab Notebook

[xx005fs]

Originally Posted by axn

In my timing runs, a T4 was only about 15% slower than K80 (since you get only half a K80 in colab).

Try this - when you get a T4, use it run your PRP. After 1-2 hours, kill the run and ask for a new GPU session. There is a high chance you will get a P100 or a K80.

Interesting. Based on my experience the T4 is significantly slower though, like 6000+ vs K80's 3000 or so. Will experiment that tomorrow cuz i've reset so many times that google isn't giving me back ends anymore.

[bayanne]

Where in the Colab notebook can you select the options of which exponent level to factor to?

[LaurV]

Originally Posted by kriesel

So that's where they've all gone.

[chalsall]

Originally Posted by bayanne

Where in the Colab notebook can you select the options of which exponent level to factor to?

I'm presuming you're referring to the GPU72_TF Notebook?

Go to your Notebook Access Keys list, and click on the link in the "GPU Work Type" column for the Instance Name you want to change.

The options are "Let GPU72 Decide" (currently TF to 75 in the high 99M range), "LL Breadth-First" (to 73 in 100M), "DC Depth First" (to 77 in 95M), and then similar DC TF options.

[bayanne]

Originally Posted by chalsall

I'm presuming you're referring to the GPU72_TF Notebook?

Go to your Notebook Access Keys list, and click on the link in the "GPU Work Type" column for the Instance Name you want to change.

The options are "Let GPU72 Decide" (currently TF to 75 in the high 99M range), "LL Breadth-First" (to 73 in 100M), "DC Depth First" (to 77 in 95M), and then similar DC TF options.

Thanks

[bayanne]

The results are now being automatically being passed to PrimeNet, no doubt a result of your endeavours :)
Showing up as GPU72_TF in my results but seemingly creditted to my account

All that didn't get passed to Primnet was when a factor was found

[Uncwilly]

Originally Posted by bayanne

The results are now being automatically being passed ....

All that didn't get passed to Primnet was when a factor was found

From another thread

Originally Posted by chalsall

The automatic submission of completed work by Colab Instances is now (almost completely) working. The only thing left to do is handle "Factor Found" messages. I'm waiting for one of my own instances to find a factor so I can test the code path.

For those who's Primenet Username (not Display Name) I already knew, I've activated this. Basically, within a minute of a result being returned to GPU72, it is then sent to Primenet, and credited at both locations.

I have a "Factor Found" in my account. Chris will be using this one as his test bed.

[Chuck]

Originally Posted by chalsall

A new personal record... Six (6#) T4s running simultaneously!!!

And over-night, one T4 lasted 11 hours, while three others lasted 10 hours each!

I have been using the paid tier (Colab Pro) since Feb 7. I get sessions that last at least 24 hours, and one went as long as 32 hours (usually with P-100). So far I have been using two sessions at a time.

I don't want to get banned or restricted, so I am hesitant to try any additional concurrent sessions. It's not clear how much usage is actually going to be allowed. I've certainly got my $9.99 worth so far.

[kracker]

https://twitter.com/GoogleColab/stat...29213560610818

[ric]

A very minor issue: just submitted 5 results, all of which were considered "not needed", since someone else had already performed those same bitlevels. Log attached.

This is just to leave track of what happened, no request for action from my side.

[Uncwilly]

Originally Posted by ric

A very minor issue: just submitted 5 results, all of which were considered "not needed", since someone else had already performed those same bitlevels. Log attached.

Did GPU72 auto submit it for you?
https://www.mersenne.org/report_expo...exp_hi=&full=1
I checked all the exponents in the file that you posted and it looks like you got credit for each. Look at your account and see which machine is listed.