[QUOTE=penlu;491099]Now I have another question---why is gpu72 handing out TFing for ~93M only up to 72 bits, esp. when TF to a given bitlevel is easier at higher exponents?[/QUOTE]

I know you've already answered your own questions, but to expand for context...

Some like to do higher candidates to lower bit levels because more factors are found per GHzDays, as well as "wall-clock time". This might be because they have slower GPUs, or because they just like finding lots of factors.

And this is perfectly fine. The rule around the GIMPS project is everyone's allowed to do whatever they want (this is a volunteer effort, after all), so long as it doesn't negatively impact on anyone else. As in, all work is appreciated, except for "poaching" (read: doing work assigned to someone else).

GPU72 was created to facilitate the coordination of GPU Trial Factoring; originally such efforts were actually coordinated via emails, and occasionally "toes were stepped on".

TL;DR: TF'ing to 72 bits in the 90s is still valuable to the GIMPS project in the long term, but going to 76 in the high 80s is more immediately useful.

Quick status update...
 

Hey all. Just a quick update.

Thanks to everyone who stepped up to provide some fairly serious GPU compute to help with the "to 76 bit" Trial Factoring crunch.

We now have about a three month buffer of candidates "optimally trial factored" ahead of Primenet's P-1'ers.

[QUOTE=chalsall;492328]Hey all. Just a quick update.

Thanks to everyone who stepped up to provide some fairly serious GPU compute to help with the "to 76 bit" Trial Factoring crunch.

We now have about a three month buffer of candidates "optimally trial factored" ahead of Primenet's P-1'ers.[/QUOTE]

That was efficient and effective.

If anyone is so inclined you are welcome to redirect your efforts to GPU72 DC TF and help the DC progress

[QUOTE=petrw1;492329]That was efficient and effective.

If anyone is so inclined you are welcome to redirect your efforts to GPU72 DC TF and help the DC progress[/QUOTE]
Chris let me know the status of things, so I have DCTF enqueued for when the LLTFs finish. :smile:

[QUOTE=kladner;492425]Chris let me know the status of things, so I have DCTF enqueued for when the LLTFs finish. :smile:[/QUOTE]

Yeah, I saw that. Thanks. :smile:

GPU72 is also managing DCTF'ing ahead of the DC wavefront. And it's currently targeted to help Wayne's (aka petrw1) sub-project of getting 0.1M ranges below 2,000 un-factored candidates (while at the same time helping the GIMPS DC effort).

Interestingly, Oliver Kruse completed his 1,000+ manually reserved P-1 assignments in the 87M range a couple of days ago, and then reserved another 1,000+ in 88M. Excellent!

While this tightens the temporal buffer a bit, we're still looking good.

Thanks for the compute everyone! :tu:

[QUOTE=chalsall;492490]GPU72 is also managing DCTF'ing ahead of the DC wavefront. And it's currently targeted to help Wayne's (aka petrw1) sub-project of getting 0.1M ranges below 2,000 un-factored candidates (while at the same time helping the GIMPS DC effort).
[/QUOTE]

I switched MISFIT over to Double Check, Let GPU72 Decide. It has already begun downloading DC TF.

[QUOTE=Chuck;492491]I switched MISFIT over to Double Check, Let GPU72 Decide. It has already begun downloading DC TF.[/QUOTE]

Thanks Chuck.

The nice thing about DCTF is there is a finite amount to complete; unlike LLTF which will go on forever (or, at least, as long as most of us are still using deterministic compute)....

The nice thing about LLTF is the big spike in Work Saved when a factor is found. :smile:

[QUOTE=kladner;492495]The nice thing about LLTF is the big spike in Work Saved when a factor is found. :smile:[/QUOTE]M9999999491 has a factor: 19999998983
"you just saved 551,667 GHz-days" :leaving:

[QUOTE=James Heinrich;492496]M9999999491 has a factor: 19999998983
"you just saved 551,667 GHz-days" :leaving:[/QUOTE]
I am not so ambitious. I was just doing wave-front LLTF. While it is insignificant in real terms, I got a real charge from 2 or almost 3 factor days in LLTF. :w00t:

I have just received a couple of exponent assignments I found kind of strange since they're so large: [URL="https://www.mersenne.org/report_exponent/?exp_lo=166802869&full=1"]166802869[/URL], [URL="https://www.mersenne.org/report_exponent/?exp_lo=223488289&full=1"]223488289[/URL]

It looks like these were recently (as in today) TF'd up to 70 bits; I got the assignment to go up to 80. They're associated with an assignment ID and show up in my mersenne.org but not gpu72.com assignments. I am using primetools to get work. I assume gpu72 went down briefly and so primetools fell through to primenet...?

I have a couple of questions. Is this associated with mersenne.org going down recently? Why are these exponents so large?