[QUOTE=S34960zz;256602]The TF limits may also need re-weighting to allow for the huge change in TF productivity due to GPU computing contributions.[/QUOTE]

Agreed....

OR if the server can tell if a PC requesting TF is using the GPU the server could assign it an extra bit of TF just ahead of the LL wavefront.

[QUOTE=petrw1;256613]If your worktype is TF you will get assignments in the 80M range.
If TF-LMH; then in the 180M range.[/QUOTE]
petrw1,

Hmm... the "Worker Windows" setting for that P233 that's doing TF in the (now) 180M range is "First-time tests." I assure you, I haven't requested (and didn't even know that I was doing) any work in the LMH area!

I imagine that the automatic assignment to that range has to do with the limited capabilities of that processor. So could I say that my puny P233 is doing work "beyond the wavefront"? :smile:

Rodrigo

[QUOTE=Rodrigo;256618]setting for that P233 that's doing TF in the (now) 180M range is "First-time tests."[/QUOTE]You asked the server for first-time LL work, but the server looked at what kind of system it is and said "no, you're too slow for that" and gave you what it thought was the most suitable kind of work for your CPU.

There's two sets of automatically-assigned TF work: TF-LMH will do trial factoring up to low limits only (2^65 or so), which (due to limited supply of unfactored exponents) is now out around 180M. Regular TF works a little bit ahead of the first-time LL tests and bring the exponents up to a higher bit depth (2^70 or so). After that the P-1 work is done, then LL, then finally double-check LL. TF-LMH is way ahead of the first-time LL (+130M); TF is well ahead of LL (+30M), and P-1 is struggling to keep in front of LL (in fact it's not, and many P-1 are of necessity done by LL workers, many times not as well as they should be).

Thanks, James.

I'd thought that in order to do LMH work one needed to volunteer specifically for it, but I guess this is one circumstance where things work differently.

My understanding of GIMPS (and PrimeNet) gets better every week, thanks to folks like you and petrw1 who patiently explain things. Much appreciated!

Rodrigo

[QUOTE=ckdo;256582]Perhaps the "do last bit of TF after P-1" change should be undone in order to effectively halve that gap within a foreseeable timeframe.[/QUOTE]

It appears they may have heard you.
There are over 19,000 new TF assignments available in the 54M range now.

And I have 3 of them - all to 2^69; the last bit.

And if this continues you will have that much more time to finish the 90M range

A milestone of sorts....
 

By moving P-1 up to the 53M range there are now over 15,000 LL tests ready in the 53M range.

I'm curious to see if that is enough of a head start to keep P-1 from holding up LL for a while.

LL is getting close to the 53M range.

Any GPU P-1 code out there?



-- Craig

If there is, I am so getting a new GPU.

[QUOTE=nucleon;257643]Any GPU P-1 code out there?



-- Craig[/QUOTE]

Give me a pointer to a (somewhat easy) P-1 implementation, and I'll try to recode it for a GPU... :smile:

(as long as George is not working on it already)

Luigi

I just did a little analysis...I did the LL Results report for the last 13 days.

I only counted first time LL tests in the 37-53M ranges and excluded double checks. 42% were in the 5xM range.
Over those 13 days the average was just over 180 LL completions per day.

I know of no way to similarly count P-1 completions in the required range; nor to determine which are P-1 only and which are P-1 required before the LL tests for the same PC on the same exponent.

In the last Recent Results (46 minutes worth) there were 8 P-1 completions in the 4x-5xM ranges but that is a pretty small sample.

With a current LL "capacity" of 180 per day the project needs at least as many P-1 completions in the current LL range to keep up. Actually about 6% more than that to allow for those that find a factor.

So, at roughly [url=http://mersenne-aries.sili.net/prob.php?exponent=53000000&b1=585000&b2=14625000]4.15GHz-days[/url] per P-1, we need (4.15 * 180 * 1.065) = 796GHz-days/day of P-1 power to keep up with LL.