All is well...thanks for quick fix.

I like the way the results submission process for Colab works using the GPU72_TF computer name. This separates out the work on my PrimeNet CPU report so I can see how much is coming from Colab.

[QUOTE=chalsall;537672]The automatic submission of completed work by Colab Instances is now (almost completely) working.
For those who's Primenet Username (not Display Name) I already knew, I've activated this.[/QUOTE]I notice that the returned results are queued in GPU72 for a minute or so, which is fine, but the text shown below says:[quote]Copy and paste the above results lines (only those in the green cell) into the Primenet Manual Results page.
Or, better yet, please email us with your Primenet USERNAME (but NOT your PASSWORD), and the results will be submitted automatically.[/quote]Perhaps it would be better to show that only for users for whom automatic submission is not enabled, and for those for whom it is to display something like "the above result(s) will be sent to Primenet automatically within a minute or so".

[QUOTE=James Heinrich;537796]Perhaps it would be better to show that only for users for whom automatic submission is not enabled, and for those for whom it is to display something like "the above result(s) will be sent to Primenet automatically within a minute or so".[/QUOTE]

Thanks... I often forget about the humans... :wink:

So, it appears that Colab is definitely viable again! A massive thanks to Google for all the compute. I have to assume they understand, and are tolerant of, what we're up to. :tu:

Because of this, I have invested the time in getting the GPU_TF Notebook to also run CPU jobs in parallel. This is close to being ready for production -- will be running initially with some beta testers (beyond just me).

Although, to be honest, there's not a whole lotta power there. Only a single (hyperthreaded) core of a Xeon @ 2.30GHz. 12G of RAM, though, so good for (slowish) P-1'ing. And a pity to just let it sit there idle.

In preparation for taking this "live", I have enabled the GUI function for CPU Worktype selection at the [URL="https://www.gpu72.com/account/instances/"]Instance List and Edit pages[/URL]. Note that by default every instance is set to "Let GPU72 Decide" -- I haven't actually figured out what makes sense yet. Perhaps some ECM'ing?

But, importantly, anyone who doesn't want a CPU job to be run in parallel, please choose the "Disabled" option. Then the CPU is left for whatever you might want to do with it.

Pointing out of SPE's appreciated. As are thoughts and suggestions.

[QUOTE=chalsall;537928]Because of this, I have invested the time in getting the GPU_TF Notebook to also run CPU jobs in parallel. This is close to being ready for production -- will be running initially with some beta testers (beyond just me).[/QUOTE]
me me me :jcrombie: pick me

[QUOTE=chalsall;537928]I have invested the time in getting the GPU_TF Notebook to also run CPU jobs in parallel.[/QUOTE]Thanks for doing this, I was hoping you would. :tu:

GPU Work Type
 

I just noticed today that a Notebook Access Key that I had set to LL TF (Depth First) says Unknown in the GPU Work Type column on the Notebook Access Key page ([url]https://www.gpu72.com/account/instances/[/url]). I didn't use this key today, so I don't know what type of work actually gets assigned to it.

[QUOTE=linament;537971]I didn't use this key today, so I don't know what type of work actually gets assigned to it.[/QUOTE]

Ah... Thanks. As usual, an SPE... Fixed.

This was just an error on what was displayed to the humans on that one page. The fetch would have gotten the work-type actually set.

Looking forward to this :)

[QUOTE=bayanne;538002]Looking forward to this :)[/QUOTE]

Yeah... It will be good to do a bit of CPU work on the side (and/or, when GPUs aren't available).

Please keep in mind that these CPUs are not that quick. ~30 running hours for a Cat 2 P-1 (done "well", though).

[QUOTE=chalsall;537928]I have invested the time in getting the GPU_TF Notebook to also run CPU jobs in parallel. This is close to being ready for production -- will be running initially with some beta testers (beyond just me).

Although, to be honest, there's not a whole lotta power there. Only a single (hyperthreaded) core of a Xeon @ 2.30GHz. 12G of RAM, though, so good for (slowish) P-1'ing. And a pity to just let it sit there idle.[/QUOTE]Excellent. A core is a terrible thing to waste. Especially if it's among dozens or hundreds.

These first-PRP tests were all done by mprime on those single Colab Xeon cores, sometimes hyperthreaded and sometimes not, with permanent storage on Google drive to bridge the brief runs.

[CODE]86939693 Kriesel colab 57990AE5CDD378__ 30388581 1 3 2019-12-20 00:52
87092557 Kriesel colab B26A478128F5A9__ 27398510 1 3 2019-12-29 20:11
90417403 Kriesel colab 506CACA072C1F7__ 61584056 1 3 2020-02-01 21:58
90808273 Kriesel colab 711968184E7EE8__ 63588385 1 3 2020-02-17 07:28[/CODE]

[QUOTE=kriesel;538042]Excellent. A core is a terrible thing to waste. Especially if it's among dozens or hundreds.[/QUOTE]

Yeah... I don't think we'll ever get into the hundreds, but I am designing this to be ready to scale... :wink:

Amusingly, one of my beta test runs actually just found a factor (Stage 1)!

Man, "cloud" is fun!!! :tu:

[CODE]
20200221_185700 DEEP: BS: [Work thread Feb 21 18:57] M92729447 has a factor: 185587507878894135482237279303 (P-1, B1=720000)
20200221_185700 DEEP: BS: [Comm thread Feb 21 18:57] Sending result to server: UID: [REDACTED]/Colab_iROOT, M92729447 has a factor: 185587507878894135482237279303 (P-1, B1=720000)
20200221_185700 DEEP: BS: [Comm thread Feb 21 18:57]
20200221_185701 DEEP: BS: [Comm thread Feb 21 18:57] PrimeNet success code with additional info:
20200221_185701 DEEP: BS: [Comm thread Feb 21 18:57] CPU credit is 3.7816 GHz-days.
20200221_185701 DEEP: BS: [Comm thread Feb 21 18:57] Successfully quit GIMPS.
[/CODE]