GPU to 72 status... - Page 12

petrw1 · 2011-12-20, 17:05

Quote:

Originally Posted by James Heinrich

I'm pretty sure by "GPU-P1" and "GPU-DC" petrw1 is referring to assignments from www.gpu72.com as opposed to actually doing the work on a GPU.

Gold star for James

kladner · 2011-12-20, 19:17

Quote:

Originally Posted by petrw1

Gold star for James

Make that two!

Dubslow · 2011-12-20, 22:39

I'll put at least one core on P-1 duty... after I'm done with some DC AVX testing...
Maybe more, depending on how much LL/DC I want to do... (though with petrw1 on DC duty the milestone should be just fine, so I think it'll be LL or P-1... I do need one core for the 460...) we'll see. I'll stick with one core for now.

Mini-Geek · 2011-12-21, 02:48

Quote:

Originally Posted by petrw1

let's hope there will be others to take over my share of P-1 (15 per day).

I currently have 3 cores running P-1, completing 3/day. I added these about 10 days ago. I might get more memory soon, in which case I could bump it up to all 4 cores and so approximately 4/day. Not much compared to 15/day, but much better than nothing!

Dubslow · 2011-12-21, 04:14

Quote:

Originally Posted by Mini-Geek

I currently have 3 cores running P-1, completing 3/day. I added these about 10 days ago. I might get more memory soon, in which case I could bump it up to all 4 cores and so approximately 4/day. Not much compared to 15/day, but much better than nothing!

Mine is not quite 2/day with one core. Could be 2 if I let it use the lower bounds of 72 bits.

garo · 2011-12-21, 19:15

We seem to be out of P-1 candidates <50M and factored to 72 bits. Did you do a mass unreservation or is P-1 suddenly so popular?

chalsall · 2011-12-21, 19:19

Quote:

Originally Posted by garo

We seem to be out of P-1 candidates <50M and factored to 72 bits. Did you do a mass unreservation or is P-1 suddenly so popular?

The latter.

Dubslow · 2011-12-21, 21:56

Can I request you list the expiration times in the 'View Assignments' report? I had accidentally reserved a good three months of work of TF, and the half of it I had not done expired a couple of days ago while I was servicing those without GPU's. If it weren't for the fact that I can't get mfaktc-0.18 to work, I wouldn't have noticed that they had expired and would have been chugging through them.

chalsall · 2011-12-21, 22:12

Quote:

Originally Posted by Dubslow

Can I request you list the expiration times in the 'View Assignments' report? I had accidentally reserved a good three months of work of TF, and the half of it I had not done expired a couple of days ago while I was servicing those without GPU's. If it weren't for the fact that I can't get mfaktc-0.18 to work, I wouldn't have noticed that they had expired and would have been chugging through them.

Take the "Assigned" date, add one to the month. if ($Month == 13) { $Month = 1; $Year++; }

I also highlight in red (and add an asterisk) any assignment which is within five days of expiring on the "View Assignments" page.

I'm not sure what else I can do, other than perhaps automatically e-mailing users when they are at risk of having assignments expire.

petrw1 · 2011-12-21, 22:18

Quote:

Originally Posted by chalsall

Take the "Assigned" date, add one to the month. if (Month == 13) { $Month = 1; $Year++; }

I also highlight in red (and add an asterisk) any assignment which is within five days of expiring on the "View Assignments" page.

I'm not sure what else I can do, other than perhaps automatically e-mailing users when they are at risk of having assignments expire.

Just noticed I have a few that are 30 days old today but no red asterisk.
Does this only apply to TF? Mine are P-1. I may also have some DC or LL in the future that will be more than a month old.

chalsall · 2011-12-21, 22:25

Quote:

Originally Posted by petrw1

Just noticed I have a few that are 30 days old today but no red asterisk. Does this only apply to TF? Mine are P-1. I may also have some DC or LL in the future that will be more than a month old.

Sorry; should have been clearer.

TF work expires after a month unless an extension is requested. This is clearly stated on the assignments page.

P-1 work expires after three months.

DC/LL work is formally transferred to the control of PrimeNet, so its expiration policy governs.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Status	Primeinator	Operation Billion Digits	5	2011-12-06 02:35
62 bit status	1997rj7	Lone Mersenne Hunters	27	2008-09-29 13:52
OBD Status	Uncwilly	Operation Billion Digits	22	2005-10-25 14:05
1-2M LLR status	paulunderwood	3*2^n-1 Search	2	2005-03-13 17:03
Status of 26.0M - 26.5M	1997rj7	Lone Mersenne Hunters	25	2004-06-18 16:46

2011-12-20, 22:39	#124
Dubslow Basketry That Evening! "Bunslow the Bold" Jun 2011 40<A<43 -89<O<-88 3·29·83 Posts	I'll put at least one core on P-1 duty... after I'm done with some DC AVX testing... Maybe more, depending on how much LL/DC I want to do... (though with petrw1 on DC duty the milestone should be just fine, so I think it'll be LL or P-1... I do need one core for the 460...) we'll see. I'll stick with one core for now.

2011-12-21, 19:15	#127
garo Aug 2002 Termonfeckin, IE ACC₁₆ Posts	We seem to be out of P-1 candidates <50M and factored to 72 bits. Did you do a mass unreservation or is P-1 suddenly so popular?

2011-12-21, 21:56	#129
Dubslow Basketry That Evening! "Bunslow the Bold" Jun 2011 40<A<43 -89<O<-88 3·29·83 Posts	Can I request you list the expiration times in the 'View Assignments' report? I had accidentally reserved a good three months of work of TF, and the half of it I had not done expired a couple of days ago while I was servicing those without GPU's. If it weren't for the fact that I can't get mfaktc-0.18 to work, I wouldn't have noticed that they had expired and would have been chugging through them.