Okay.

I've released everything at 70 back to GPU72, except for my assignments in progress. I've configured all my machines to fetch ->70 going forward, with a 12 hour queue.

[QUOTE=chalsall;387799]Although this probably means that, like George said, ~60,000 DC TF Cat 4 assignments will be needed; GPU72 has only appropriately TF'ed ~20,000 candidates in that range (and averaging ~250 a day).[/QUOTE]

So we need about 40,000 DCTF in the next 60 days. If we only DCTF ->70, that's a total of 2 THz-d/day. I can do half that alone. We need about 1 THz-d/day for the next two months to avoid releasing below 70 if anyone is interested in helping.

Chris, can "what makes sense" and "let gpu72 decide" issue assignments to only 70?

[QUOTE=chalsall;387815]Yes, but it's only valuable if everything below is also assigned to someone to hold for TF'ing. I'll do my be to get in touch with HBendtz to explain what's going on, and that we need to reserve all of 38M and 39M to allow GPU72 to temporarily TF to 70.

But still, this isn't going to completely mitigate the situation; some DC Cat 4 *IS* going to be released at 69 for at least the next 60 days -- we simply don't have the firepower to prevent this.[/QUOTE]

I will happily pick up some DCTF if that is desirable. The GTX 580 is currently doing just under 400 GHzD/D in the LL range.

[QUOTE=chalsall;387799]
Although this probably means that, like George said, ~60,000 DC TF Cat 4 assignments will be needed; [/QUOTE]

There are other options:

1) I could change assignments to new computers to a blend of cat4 DC and cat4 LL. Although I'd rather not.
2) I could investigate (next week) changing the expiration rules to 30 or 45 days after no contact from a computer (or user?) that has never returned a result. It would remain at 60 days for a computer (or user?) that has returned a result.

[QUOTE=kladner;387850]I will happily pick up some DCTF if that is desirable. The GTX 580 is currently doing just under 400 GHzD/D in the LL range.[/QUOTE]

That would help a lot! We have no chance of factoring to 71 bits (we need another 3 THz-d/d), but if you pledge to 70, we'll only need another 600 GHz-d/d to not release at 69.

I get ~425 in the current LL range with my GTX 580's with these settings:

GPUSievePrimes=70000
GPUSieveSize=128
GPUSieveProcessSize=16

It's only a 5% boost, but worth trying if you haven't done any tuning.

I've been running with similar numbers, though my impression was that GPUSieveProcessSize=8 might give a bit more. It's been a while since I really messed with testing that. ATM mfaktc 0.2 says it's doing 478 GHz-D/D. This is with it clocked at 861 MHz, where it seems quite happy, now that there's cooler air down by the floor.

The 400 GHz-D/D came from an estimate of where the 30 day average line is in my GPU72 Overall Statistics. :smile:

EDIT: Another hour of LLTF, and it will start on 39M DC to 70.

EDIT2: 9:15 to do one low 39M from 69-70.

Grrr... take your clothes off, I wanna [redacted] you... put your clothes back, I don't wanna [redacted] you...
Few days ago I moved my last card doing DCTF into doing LLTF because because we didn't have enough LLTF power...
(still finishing the DCTF queue, luckily, but now the queue ia already filled with LLTF assignments)
Now I have to go back home and move it back to DCTF?? :shock:
Ok, if desired, I will (happily, due to the lower bitlevel!) move all my current available power to DCTF for a while. I will do that tonight, you can count on ~1800GHzD/D of DC.

[QUOTE=Prime95;387851]2) I could investigate (next week) changing the expiration rules to 30 or 45 days after no contact from a computer (or user?) that has never returned a result. It would remain at 60 days for a computer (or user?) that has returned a result.[/QUOTE]

I think this would be a good (temporary) option. Setting it to 30 days would reduce the demand from ~60,000 to ~30,000 candidates, and based on the firepower being brought to bear we probably won't need to release TOO many at only 70.

BTW George, with your new Cat 4 assignment strategy, I think it's safe for you to set the LL Cat 4 offset to 100,000 now; no more need for the 120 step per day.

I've moved my GTX580 to DC-TF too. I think George doesn't need to resort to either option. We should be fine with LaurV and me coming to join the effort.

@George: You could look at that expiry SQL that says 60 days *and* overdue by 10 days as madpoo indicated in this post: [url]http://www.mersenneforum.org/showpost.php?p=387883&postcount=1520[/url]

[QUOTE=chalsall;387877]
BTW George, with your new Cat 4 assignment strategy, I think it's safe for you to set the LL Cat 4 offset to 100,000 now; no more need for the 120 step per day.[/QUOTE]

I'd leave it on. There is no harm. There will be plenty of Cat3 to go around.

[QUOTE=LaurV;387857]Grrr... take your clothes off, I wanna [redacted] you... put your clothes back, I don't wanna [redacted] you...
Few days ago I moved my last card doing DCTF into doing LLTF because because we didn't have enough LLTF power...
(still finishing the DCTF queue, luckily, but now the queue ia already filled with LLTF assignments)
Now I have to go back home and move it back to DCTF?? :shock:
[/quote]

:sorry:

[quote]
Ok, if desired, I will (happily, due to the lower bitlevel!) move all my current available power to DCTF for a while. I will do that tonight, you can count on ~1800GHzD/D of DC.[/QUOTE]

Please do! It looks like we're getting close enough in pledged power to factor everything needed to 71 bits.