[QUOTE=manfred4;389842]I will continue with this DCTF as well for now - with averaging 300 GHzd/d.
The people saying their firepower in the last few posts would add up to 3060 GHzd/d. I calculated we are approximately 3088000 GHzd in front of our goal relating to [URL="http://en.gpu72.com/reports/current_level/"]this[/URL] table, or ~1000 days until we're finished.[/QUOTE]

Mine is usually 1200 GHz-d/d.

Speaking of rolling averages, would it be possible to have the GHz Days per Day on the /account/assignments page be changed to a rolling average instead of an account lifetime number? Perhaps along with the calculation used on the get assignments page, too?

Though I guess that's less relevant if the functionality is being moved to PrimeNet.

[QUOTE=petrw1;389834]…"Die! DCTF Die!!!"…[/QUOTE][YOUTUBE]trfg6WIDryQ[/YOUTUBE]

We may not have enough power to move all those ranges up as per those graphs. Additionally, it does not really worth to do so. The most work is done by top-of-the-line cards, and also we have to consider the P-1 done in the range, which decreases the chances of finding factors, from about 1 in 70 to about 1 in 90. All you guys doing DC here, check your history and see how many factors you found, for how much assignments (in bitlevels) taken, how long time it took, and how many LLDC tests could you do in this time.

No need to reply, it was just rhetoric.

As I repeatedly said (didn't you find out that I am playing Davieddy here, at least since he left? :wink:), the "optimum" level for the DC would still be according with[URL="http://www.gpu72.com/reports/current_level/"] this table[/URL] (i.e. 45M@72), except that the 56M has to be moved at 73 (i.e. the last 4 cells of the "72" column in the DC table, from 56 to 59 inclusive, have to be white, and not yellow). [B][U]That is all the change we need.[/U][/B] Of course, this changes Chris' internal kitchen too, it is not only about coloring the table, but about grabbing and releasing them too, at the right moment. But I am convinced he can deal with it, assuming he wants and has time.

We can get rid of DCTF once forever, if we stay on it next year. Actually, I would (optimistically) say half year... Maybe less...

[QUOTE=LaurV;389838][URL="http://www.gpu72.com/reports/worker/2423ae6e8f696d5e7d1447de91ca35a6/"]1T8[/URL] (this means 1800GHzD/D, and I meant it when I said it) as long as we have DCTF work and no requirement for other work, at least till Thai summer comes in March/April. :smile:[/QUOTE]

OK I will continue 1T3 DCTF Let GPU72 Decide until LLTF is needed.

[QUOTE=LaurV;389913]The "optimum" level for the DC would still be according with [URL="http://www.gpu72.com/reports/current_level/"]this table[/URL] (i.e. 45M@72), except that the 56M has to be moved at 73 (i.e. the last 4 cells of the "72" column in the DC table, from 56 to 59 inclusive, have to be white, and not yellow). [B][U]That is all the change we need.[/U][/B]

We can get rid of DCTF once forever, if we stay on it next year. Actually, I would (optimistically) say half year... Maybe less...[/QUOTE]

OK, this table has been updated. Taking 56M to 59M to 73 "bits" [URL="https://www.gpu72.com/reports/estimated_completion/primenet/"]only adds ~28 days of additional work[/URL]; ~258 days total (and dropping as the rolling average stablizes to the fire-power being applied). Note that 59M and above is already all at 73 or above.

[QUOTE=LaurV;389913]you guys doing DC here, check your history and see how many factors you found, for how much assignments (in bitlevels) taken, how long time it took, and how many LLDC tests could you do in this time.

No need to reply, it was just rhetoric.
.[/QUOTE]

My rhetoric reply: 22 / 1395 = .01577% = 1/63.4
Mostly 70-71; a couple dozen 69-70
Beating the odds.

[QUOTE=petrw1;389974]My rhetoric reply: 22 / 1395 = .01577% = 1/63.4
Mostly 70-71; a couple dozen 69-70
Beating the odds.[/QUOTE]

Hmm, since I don't know of an opencllucas, I could have done 31 dc in the last 26d, but found 134 of 13400 (92% @70-71)

Yeah, my last submission was 2/220.

[QUOTE=chalsall;389953]OK, this table has been updated. Taking 56M to 59M to 73 "bits" [URL="https://www.gpu72.com/reports/estimated_completion/primenet/"]only adds ~28 days of additional work[/URL]; ~258 days total (and dropping as the rolling average stablizes to the fire-power being applied).[/QUOTE]
Beautiful! Thanks a billion.
[QUOTE] Note that 59M and above is already all at 73 or above.[/QUOTE]
Guess who moved it? :razz:

[QUOTE=TheMawn;389986]Yeah, my last submission was 2/220.[/QUOTE]

Last 12 months - 995/61687 = 1.61%

Mixture of types from gpu72

62/3013 DC = 2.05% (many to 72, quite a few to 73 bits)

21/1741 LL = 1.2%

The other 57,000 were ranges picked by hand