[QUOTE=chalsall;388330]we could go for several months without doing any additional LL TF'ing and still not hand out anything at less than 74.[/QUOTE]

Alright. This is an important statement. I will finish my week or so worth of LLTF and switch to DCTF.

Just a logistical question about GPU72: If I completed some work and submitted the results to Primenet but unreserved the work from GPU72.com before it had a chance to "see" that I finished the work, what happens?

I don't know, but GPU72 checks at least every hour (or half hour?) so if you wait an hour before unreserving you're good.

I thought "Let GPU72 Decide" was going to start handing out DC work, but the last batch I just received (via MISFIT) was 73M 71 to 74 bits.

Giving her all she can take, Captain! :max:

EDIT: :wink:

[QUOTE=chalsall;388348]If. Such an important word... :wink: :smile:

Until we pull out of this (downward) glide in DC, it might be fun to "watch the numbers" and possibly react (or not). :smile:[/QUOTE]

Down to 1,068 yesterday :(

[QUOTE=TheMawn;388357]Just a logistical question about GPU72: If I completed some work and submitted the results to Primenet but unreserved the work from GPU72.com before it had a chance to "see" that I finished the work, what happens?[/QUOTE]

The Internet crashes... :wink:

Seriously though, GPU72 will observe (within an hour) that the work completed, but won't credit you. There will be up to a one hour window where GPU72 might assign the work to another worker, thus wasting cycles.

Thus, if you're going to unreserve work, it would be best to submit everything done, clear everything else out of your worktodo.txt file(s), and reserve new work. Then, wait two hours (just to be sure), and then unreserve the remaining work.

[QUOTE=Chuck;388361]I thought "Let GPU72 Decide" was going to start handing out DC work, but the last batch I just received (via MISFIT) was 73M 71 to 74 bits.[/QUOTE]

I didn't implement the code change yesterday; I have today (including the preview).

[QUOTE=chalsall;388390]I didn't implement the code change yesterday; I have today (including the preview).[/QUOTE]

Thanks.

I changed the recycling SQL to expire DCs after 40 days of no contact if the computer has never returned an LL result.

Honey I'm Home!!!!!!!!!!!!!!!!
 

Have GPU will Travel....or in this case DC.

Just got my first 100 x 37M DC to 71 bits.
Screen suggests 18 minutes per assignment. Is this good?
My rough Math tells me it will be about 500GhzDays / Day.

GTX 970 mfaktc 0.20

No fiddling with the ini file yet...I suspect the defaults are not best suited for my card?

Have to get the Grandkid to bed first.

[QUOTE=petrw1;388422]Have GPU will Travel....or in this case DC.

Just got my first 100 x 37M DC to 71 bits.
Screen suggests 18 minutes per assignment. Is this good?
My rough Math tells me it will be about 500GhzDays / Day.
[/quote]

That's great!

[quote]
GTX 970 mfaktc 0.20

No fiddling with the ini file yet...I suspect the defaults are not best suited for my card?
[/QUOTE]

The defaults will be okay, but there's usually room for improvement.

The three that matter are:

GPUSieveProcessSize
GPUSieveSize
GPUSievePrimes

I would adjust them in that order. As soon as you see a GHz-d/day number you've run it long enough. CRTL-C and adjust. There are only a few values for the first two, and I'd adjust GPUSievePrimes by jumps of 5000 or so.