Wow!!! What a week!
 

An exciting week around here! :smile:

So everyone in "TF Land" knows...

The unprecedented surge in LL/DC assignment requests from Primenet is going well. The new Primenet policy of giving new users DC Cat 4 work (unless they explicitly ask for LL work, in which case they're initially given LL Cat 4) has worked out perfectly.

But thank goodness the "RIP DCTF" team had made so much progress! For a while there were over 600 DC requests an hour, and even now we're still seeing somewhere around 250 to 300 requests an hour. We're still years ahead, but it was good that such a large buffer existed!

What was somewhat unexpected was the number of new users explicitly asking for LL work. While we had (and still have) a reasonable buffer for LL Cat 4, additional firepower was redirected from low LL Cat 3 to low Cat 4 to ensure we remained "good".

As far as I can tell, not a single assignment was issued by Primenet for DC'ing nor LL'ing (nor PM-1'ing) not optimally TF'ed (although not always at the lowest candidate for each category).

Please know that this balancing act will be continuing for a few days longer, so those who choose "What Makes Sense" or "Let GPU72 Decide" may see their assignments bounce around the different ranges. Don't be alarmed by this.

Questions and/or comments welcome.

And, as always, thanks for all the cycles everyone! :tu:

M49 may be a good opportunity to split this thread (from the last post(s)) into a "new" one with less pages? Easier to handle and find the info? (it already contains lots of subjects together, like a "thematic ho-pouri thread" :wink:

(just saying it, but if it is a stupid idea, please ignore it and/or delete the current post)

[QUOTE=LaurV;423668]M49 may be a good opportunity to split this thread (from the last post(s)) into a "new" one with less pages? Easier to handle and find the info? (it already contains lots of subjects together, like a "thematic ho-pouri thread" :wink:

(just saying it, but if it is a stupid idea, please ignore it and/or delete the current post)[/QUOTE]
That could have advantages. I don't know what the general effect of creating a " [URL="http://www.mersenneforum.org/showthread.php?p=423668#post423668"] [/URL]GPU to 72 status...02" would be. It might prove more confusing even than 357+ posts in a thread. :confused2:

RIP DCTF...
 

Just so all those working in the DCTF range know...

The last of the DCTF candidates have now been assigned. So, I've added a "rewrite rule" such that DCTF requests instead get LLTF.

The same "Option" rules apply. As in, if "What Makes Sense" is selected the pledge level (for example, 72 or 73) is honoured. If "Let GPU72 Decide" is selected, then the pledge level is set (currently to 75).

Those who use a fetching spider such as MISFIT or mfloop may want to adjust their settings; the above was done to ensure no "fired and forgotten" systems ran dry.

[QUOTE=chalsall;423914]
The last of the DCTF candidates have now been assigned. [/QUOTE]

That is excellent news.

Chris, are you going to bring in the 62M to 74 bits for DCTF?

tl;dr:

I mean, it would make some sense, and they are only ~2000 of them. For the other marked in [URL="http://www.gpu72.com/reports/current_level/"]your table[/URL] (60M and 61M to 74) it doesn't make any sense anymore, neither for AMD cards, now that we have a better clLucas which almost can compete with cudaLucas, so you can mark them as yellow. But the 62M are not many, so there is a little bit of sense to tickle them, especially for a gtx 560, 570, or for AMD cards (good Nvidia cards like 580s or Titans are already better doing DC than DCTF, at these bitlevels).

[QUOTE=LaurV;423948]Chris, are you going to bring in the 62M to 74 bits for DCTF?[/QUOTE]

I could certainly do that, if people wanted to do that work.

But, let's wait a little while, and let the last of the 50M to 57M finish to 73 (or, at least, a good part of it).

My thinking is while we're looking good for the LLTF'ing in the various ranges, we're still "just in time" for low LL Cat 3 and Cat 4. Further, as new workers prove their commitment and stability, more and more LL Cat 3 assignments are going to start being given out. It would be good to build up a bit more of a buffer at the low end of the ranges.

Secondly, this would give those who have spiders configured to automatically get DCTF work time to adjust their settings. Some have "Let GPU72 Decide" set (which sets the pledge level), but might not want to TF to 74 (e.g. those running AMD GPGPUs).

Lastly, I would have to write a bit of code to issue appropriate LLTF assignments for anyone who has the "What Makes Sense" et al Option set. What I did yesterday was a quick and dirty "rewrite rule" hack.

tl; dr: Are there those out there who would like to take DCTF 62M to 74? 61M? 60M?

If so, please say so.

If not, now would be a good time to adjust your spider's settings to ask for LLTF.

Nothing to do with the current topic, but I notice on my individual statistics page the bottom graph is getting ugly with overlapping X-axis labels. Maybe you could limit it to no more than 8 labels so there's room?
[url]http://www.gpu72.com/graphs/worker/56f1b7572536a14513b08c88b2ba9578/[/url]

Slight tweaks to the "View Assignments" report.
 

Hey all.

Just so everyone knows, I've made some slight tweaks to the [URL="https://www.gpu72.com/account/assignments/bydate/"]View Assignments[/URL] report.

Nothing drastic. The Age and Estimated Completion columns are now rendered to a 0.01 days resolution. The Percent column now correctly takes into account the two stages of P-1'ing; previously the count would climb up to 100% during stage 1, and then drop back down and count up again during stage 2.

As always, please tell me if I've made a SPE anywhere.

What would the impact be to GPU-to-72 if the LL assignment rules changed to encourage more machines working on cat 2 LL assignments? According to the work distribution map it looks like about 60,000 cat 2 exponents are reserved for TF.

[QUOTE=Prime95;429842]What would the impact be to GPU-to-72 if the LL assignment rules changed to encourage more machines working on cat 2 LL assignments?[/QUOTE]

It would be a Good Thing [sup](TM)[/sup]!

And I think you're mis-reading the distribution map, confusing Cat 2 with Cat 3. At the moment there are only 1,030 Cat 2s reserved for TF'ing, with 2,683 Cat 2 candidates ready for LL assignment (and another 3,452 Cat 1s).

Assigning more Cat 2 (and Cat 1) had been discussed on the Milestone thread a while ago, but that conversation seemed to have petered out. I think it would be really good if this was re-opened. The pace of Cat 1 and Cat 2 completions is very slow from a number-of-assignments perspective.