GPU to 72 status...

[James Heinrich]

Are the ranges on Individual Factoring Cost P-1 hardcoded? On my report I have scales of 45M-73M and 2^69-74, whereas I'm pretty sure I've P-1 outside both of those.

[kladner]

Originally Posted by chalsall

Always a good idea to check. SPEs abound with things moving so quickly... Oh, and I just noticed that your machine grabbed a batch through the proxy. Sweet!

I fumbled around changing P95 settings. This led to a bunch of P-1 assignments getting thrown back at one point. That machine now has 15 minutes to go on its last DC. After that, P-1 will take over.

As I remember, there is some benefit to P-1 from multi-threading, but maybe not beyond 2 cores per worker. Again, this box has 32 GiB RAM. Any opinions on running 2 versus 4 (or 8) workers on an 8 core CPU with decent memory speed for dual channel?

EDIT: The DC finished. I reset the worker windows to four with 2 cores each, 28 GiB RAM allowed, all set for P-1. Repeatedly, at startup, the first worker pulls in another DCLL. I have unreserved the DC several times and it keeps coming back. This machine has been running DC for weeks with no problems. Why can't I make the first worker run P-1?


EDIT 2: Computer properties in GIMPS was set to DC for the first worker. I change that to P-1, and worker 1 still gets a DCLL. I really don't want an LL running there. What goes on?
NOTE: I guess this maybe belongs in the PrimeNet sub-forum, but it started here, and it's troublesome to change it now.

[chalsall]

Originally Posted by James Heinrich

Are the ranges on Individual Factoring Cost P-1 hardcoded?

Sigh... Yes...

Added to my Todo list...

[chalsall]

Originally Posted by kladner

NOTE: I guess this maybe belongs in the PrimeNet sub-forum, but it started here, and it's troublesome to change it now.

OK... This is /possibly/ an SPE on my part. I seem to remember that the proxy sometimes had problems picking up when a preferred work-type was changed.

Something to try: Change the settings on Primenet, then change them on the client and have it communicate with Primenet.

If that doesn't work, PM me the machine name in question.

[chalsall]

OK, so I finally climbed into the code needed to do this. Was a /lot/ more work than I first thought (needed some rather interesting hacking; thanks to George and Aaron for the support and assistance)...

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 need to build a form for this, but if anyone who's "Colabbing" and still sees (oldish) results in your report, please PM me your Primenet USERNAME (but NOT your Password; don't need, nor want, this).

A "virtual" computer is created on Primenet for each account called "GPU72_TF". This is what the results are submitted as.

This should make people's lives a whole lot easier. Just spin up an instance, and then forget about it (for a while).

[Chuck]

Originally Posted by chalsall

OK, so I finally climbed into the code needed to do this. Was a /lot/ more work than I first thought (needed some rather interesting hacking; thanks to George and Aaron for the support and assistance)...

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.

Good work. A very welcome addition.

[Chuck]

Originally Posted by chalsall

Because of the recent availability of Colab again, it would be good if people choose "LL Depth First" for at least a few of their Instances. This will assign work to 77 bits in the high 106M range.

I thought WMS always reflected your requirements at the moment.

[chalsall]

Originally Posted by Chuck

I thought WMS always reflected your requirements at the moment.

It generally does. Although for Colab I don't have a WMS, but instead a "Let GPU72 Decide" (LG72D).

It can be a bit of a shock for people to suddenly get the "heavy" work, so I generally keep LG72D to be no more than 76 bits, and leave the "Depth" setting for those who understand what they're committing to (with LG72D prepping the work for the last step).

It's a constant juggle; keep the TF'ers happy, while keeping the P-1'ers and LL'ers fed...

[Chuck]

Oh I forgot that Colab was "Let GPU72 Decide" instead of WMS.

[Chuck]

My COLAB sessions are not getting new work.

The last number I factored was 102995749, and then the session exited. I tried creating a new notebook but it still did not fetch work. I had just changed to "Depth first".

I changed back to GPU72 Decides and it successfully fetched work again.

[chalsall]

Originally Posted by Chuck

I had just changed to "Depth first". I changed back to GPU72 Decides and it successfully fetched work again.

Stick a fork in me; I'm done!

Sorry... SPE... I was trying to retarget to 102M, but forgot to change the low value. DWIM!!!

This should be working again; thanks for attempting Depth. Heading to bed now; will confirm sanity in the morning (of my code, not me. I'm definitely certifiable...).