GPU to 72 status... - Page 104

kladner · 2012-04-15, 01:08

Quote:

Originally Posted by KyleAskine

I just turned in my very first piece of work going to 72

Congrats! How long did 71-72 take, in what exponent range?

KyleAskine · 2012-04-15, 02:26

Quote:

Originally Posted by kladner

Congrats! How long did 71-72 take, in what exponent range?

Not really sure for the time, but something pretty low, in the 48M range or so. I just did 'whatever the system thinks is best' or whatever.

It is much faster now that BDot has sped everything up for us AMD folk!

garo · 2012-04-15, 10:05

Quote:

Originally Posted by chalsall

Yes, it was. 80 GD/D to be exact. It's now 20 GD/D.

Sorry about that.

Feel free to unreserve what you were assigned, and claim lower candidates.

No probs. I'll finish what I have.

James Heinrich · 2012-04-15, 12:25

Quote:

Originally Posted by chalsall

80 GD/D to be exact. It's now 20 GD/D.

Can this value be displayed on each user's Overall Statistics table? There's currently a total GHz-days column, but no per-day average. Actually overall-average and last-30-days-average would both be interesting, if they're not hard to calculate.

bcp19 · 2012-04-15, 14:14

Quote:

Originally Posted by James Heinrich

Can this value be displayed on each user's Overall Statistics table? There's currently a total GHz-days column, but no per-day average. Actually overall-average and last-30-days-average would both be interesting, if they're not hard to calculate.

Overall average can be found if you goto View Assignments. Since I had gradually added cards to GPU72, my average is just over 1/2 my current level.

James Heinrich · 2012-04-15, 15:33

Quote:

Originally Posted by bcp19

Overall average can be found if you goto View Assignments.

It can, but I still think it would be relevant to put on the individual Overall stats page.

petrw1 · 2012-04-16, 22:36

Quote:

Originally Posted by chalsall

We currently hold about 42 days of LL Trial Factoring work.

Curiously, about 25 days later we are still at 42.
At the time of this original copletion estimate did GPUto72 NOT have exponents all the way to 59M counted in this range?

In the same period the primenet range dropped from 200 to 150.
Does this just mean PrimeNet is releasing assignments to us as quickly as we can complete them (by the way, I am using the royal "we").

Dubslow · 2012-04-16, 23:13

Quote:

Originally Posted by petrw1

Curiously, about 25 days later we are still at 42.
At the time of this original copletion estimate did GPUto72 NOT have exponents all the way to 59M counted in this range?

In the same period the primenet range dropped from 200 to 150.
Does this just mean PrimeNet is releasing assignments to us as quickly as we can complete them (by the way, I am using the royal "we").

The first number varies widely by what GPU272 actually has reserved (30K, 40K, 60K, etc.) and the second overall/PrimeNet stat depends on if the 60M-61M or 61-62 ranges are counted, which also depends entirely on whether or not GPU272 has any expos in those ranges.

chalsall · 2012-04-16, 23:23

Quote:

Originally Posted by petrw1

Curiously, about 25 days later we are still at 42.

According to Douglas Adams, the answer to Life, the Universe, and Everything!!!

What was the question again?

Quote:

Originally Posted by petrw1

At the time of this original copletion estimate did GPUto72 NOT have exponents all the way to 59M counted in this range?

It did. And does.

Quote:

Originally Posted by petrw1

Does this just mean PrimeNet is releasing assignments to us as quickly as we can complete them (by the way, I am using the royal "we").

More or less...

But please do note that we're being as "polite" as possible, and there are always TF assignments available below 60M for those who don't like playing with us...

To answer your question a bit more seriously, when the Estimated Completion report was written we didn't hold nearly as many candidates in the 58M and 59M ranges. If you take those out of the summary going to 73 bits, we hold just over 31.5 days of work.

Dubslow · 2012-04-17, 00:30

I operate one computer that's slow enough that I let it get P-1 from PrimeNet; it was just assigned a 52M at 72 bits (which is good, in the longrun) but why wasn't it kept by GPU272?

petrw1 · 2012-04-17, 01:19

Quote:

Originally Posted by Dubslow

I operate one computer that's slow enough that I let it get P-1 from PrimeNet; it was just assigned a 52M at 72 bits (which is good, in the longrun) but why wasn't it kept by GPU272?

Could have been someone who TF'd it outside of GPUto72 (you can check actually)....or one of the aforementioned in the previous post.

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

2012-04-17, 00:30	#1143
Dubslow Basketry That Evening! "Bunslow the Bold" Jun 2011 40<A<43 -89<O<-88 3×29×83 Posts	I operate one computer that's slow enough that I let it get P-1 from PrimeNet; it was just assigned a 52M at 72 bits (which is good, in the longrun) but why wasn't it kept by GPU272?