20141212, 18:32  #1 
1976 Toyota Corona years forever!
"Wayne"
Nov 2006
Saskatchewan, Canada
3·5·349 Posts 
RIP DCTF.
Disclaimers: GhzDays ToGo for now is a rough estimate ... ideas of how to make it somewhat accurate?
Code:
GhzDays Member 550 TheMawn 500 petrw1 300 manfred4 460 kladner 1800 LaurV 1200 Mark Rose 4810 Total 33,670 Per Week 3,000,000 ToGo 89.10 Est Weeks 1.71 Est Years 26Aug2016 Est Done Last fiddled with by petrw1 on 20141212 at 18:34 
20141212, 18:39  #2  
1976 Toyota Corona years forever!
"Wayne"
Nov 2006
Saskatchewan, Canada
3×5×349 Posts 
Quote:
That will change quite a bit shortly as many are moved back to LLTF with LetGPU72Decide. Granted once this settles the number will gradually "auto correct" itself again. Any chance we could get one more column which is the actual GhzDays to complete all the work in that row of the chart? 

20141212, 18:47  #3 
Mar 2014
Germany
2^{3}·3·5 Posts 
I calculated my Estimate by calculating the Credit for each Million range (e.g. 38,500,000 for averaging) and added them together, so it should be pretty accurate ;)
If you say, from where to go to 72 bits or even 73 bits (I think there are some, that need to go there) I can add it up to give a new and better number. 
20141212, 19:31  #4  
"Victor de Hollander"
Aug 2011
the Netherlands
10010011011_{2} Posts 
Quote:
To 72bit GTX980 @38M 71.92bits http://www.mersenne.ca/cudalucas.php?model=566 GTX580 @40M 71.96bits http://www.mersenne.ca/cudalucas.php?model=12 GTX680 @43M 72.04bits http://www.mersenne.ca/cudalucas.php?model=467 GTX780 @49M 71.93bits http://www.mersenne.ca/cudalucas.php?model=492 To 73bit GTX980 @48M 73.15bits GTX580 @50M 72.99bits GTX680 @54M 72.95bits GTX780 @65M 73.04bits So I would personally say from 40M on to 72bits and @50M to73bit, as the GTX580 is still a very popular card for TF. People with a GTX780 and who do mind their efficiency could return to LLTF or run CudaLucas instead. Last fiddled with by VictordeHolland on 20141212 at 19:32 

20141212, 20:22  #5 
Mar 2014
Germany
2^{3}·3·5 Posts 
Okay, but I think that the value in that graph is the maximum bit depth you should go, so if it says 72.9 bits, then 73 bits is just too much and you waste your effort. For my GPU that would be at 43M/55M for the next bit.
For an average 42M/53M looks reasonable. 
20141212, 20:24  #6 
"/X\(‘‘)/X\"
Jan 2013
2^{5}·3·31 Posts 
Given that all the DCTF have already had at least one LL check, we're only saving one LL check not two. Should this be factored into the bit level, too?

20141212, 20:27  #7 
Mar 2014
Germany
2^{3}×3×5 Posts 
That and the fact, that P1 is done already is factored in, as you can see there are two lines in those charts, one for DCTF and one for LLTF

20141212, 20:41  #8 
"Victor de Hollander"
Aug 2011
the Netherlands
10010011011_{2} Posts 
But isn't the number listed (for instance 71.95) at the start of the range? In that case we should increase the bitlevel halfway, for instance between 40,000,000 and 41,000,000 ?

20141212, 20:42  #9 
"/X\(‘‘)/X\"
Jan 2013
5640_{8} Posts 

20141215, 01:58  #10 
1976 Toyota Corona years forever!
"Wayne"
Nov 2006
Saskatchewan, Canada
3·5·349 Posts 
Sunday Night Wrapup
From here http://www.gpu72.com/reports/workers/dctf/week/
115,508 GhzDays DCTF in the last week. 59 different contributors 238 Factors found 13,123 P1/LL/DC work saved. From here: http://www.gpu72.com/reports/workers/dctf/ 31 contributors currently have assignments 8,856 Assignments out. From here: http://www.gpu72.com/reports/estimat...tion/primenet/ 238.1908 estimated days to completion August 6, 2015 
20141215, 03:27  #11 
"/X\(‘‘)/X\"
Jan 2013
2^{5}×3×31 Posts 
LG72D has been switched from DCTF to LLTF. That's probably what dropped the participants.
It also looks like the throughput has dropped from 18 THzd/d to 13 THzd/d. The time to estimated completion is now 240 days and still dropping several days a day, so we should be done in less than 8 months from now. 
Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
Getting unneed DCTF work  Mark Rose  GPU to 72  4  20180101 06:14 