Heehee
[code]
Factors Found
P-1 404[/code]

[QUOTE=Dubslow;293158]Is this a result of the discussion between George and Chris? Because if so, I approve :smile:[/QUOTE]

And if it wasn't because of a discussion between George and myself, would you disapprove? :smile:

This is something I've been wanting to do for a while. Several people (including you and davieddy) have complained on the negative impact we've been having on the /primenet/ report. I didn't like it myself.

[QUOTE=Dubslow;293158]My questions are, how does Spidey find low expos that aren't reserved for LL? Does it still reserve them as LL and then immediately unreserve/rereserve as TF? Does Spidey get special treatment from PrimeNet to make sure a candidate isn't lost again?[/QUOTE]

Answers in order:

1. Spidy uses a variety of techniques to get candidates.

2. Some are still reserved as LL/DC, but are then shortly later unreserved/rereserved as TF.

3. Spidy gets no special treatment from Primenet. But the transfer window is less than a second, and if we lose a candidate in the process it's not the end of the world.

4. To answer an unasked question: in order to transfer those candidates which were already owned by workers while minimizing the loss risk I waited until after midnight UTC when a lot of "low-hanging fruit" became available, and then ran the transfer script from lowest to highest candidates.

4.1. This was a one-off event -- the assignment scripts only assign work which are already reserved from PrimeNet as TF.

5. To answer another unasked question: yes, I will soon be doing the same thing for the P-1 work type.

Sweet!

[QUOTE=chalsall;292913]And I have reason to beleive I know why you wanted a page like [URL="http://www.gpu72.com/reports/workers/saved/"]Workers' Overall Progress sorted by GHz Days Saved[/URL]... :smile:[/QUOTE]

Yep, sort is working fine now :)

-- Craig

:rant:

[QUOTE=nucleon;293239]Yep, sort is working fine now :)[/QUOTE]

Seems to be broken again... :smile:

Also, it's fun watching Pete and Greg keep switching between the [URL="http://www.gpu72.com/reports/workers/graph/3-12/"]#3 and #4[/URL] positions....

[QUOTE=chalsall;293316]Seems to be broken again... :smile:

Also, it's fun watching Pete and Greg keep switching between the [URL="http://www.gpu72.com/reports/workers/graph/3-12/"]#3 and #4[/URL] positions....[/QUOTE]

I'm glad we can keep you amused.

[QUOTE=bcp19;293319]I'm glad we can keep you amused.[/QUOTE]

What can I say... I don't get out much.... :smile:

Change to P-1 assignment policy...
 

Hey all. So everyone knows... I was doing a review of current P-1 assignments, and found some issues...

Some users have some [U][I]very[/I][/U] old assignments still outstanding, even though they are currently reserving new work. Others have bitten off a bit more than they can reasonably "chew"...

Additionally, I think it's unreasonable for P-1 assignments to be valid for three months, when it only takes at most a couple of days per modern core. That was short-sighted of me when I implemented the P-1 option.

So, I have added the same type of sanity check when people try to register new P-1 assignments as already exists for TF work -- if someone has old assignments, or more than they can process within a month, they are warned rather than given more.

I will "grandfather" current assignments, but new assignments (as of tomorrow) will expire after one month unless extended. I haven't yet, but will add highlighted notices of those P-1 assignments which are past due on the View Assignments page.

Also, P-1 assignments are now only available for candidates which have already been trial factored to 72 or more bits. My thinking here is it doesn't make sense to do a more expensive P-1 run when a much more efficient GPU TF run could find the low factors. In addition, to have the P-1 assignments appear as such on PrimeNet they will have to be transfered to another "state", and I don't want to lose any which have not already been maximally TFed.

Lastly, just so people know, as Dubslow predicted, we currently have more P-1 work than we can handle, and are thus beginning to throw back to PrimeNet those canadidates we can't reasonable handle within about a week. The good news here is it seems there are many P-1 workers taking the work through PrimeNet rather than them going to LL workers.

As always comments, and/or corrections to my thinking, welcomed and encouraged.

:goodposting:
[QUOTE=chalsall;293336]
I will "grandfather" current assignments, but new assignments (as of tomorrow) will expire after one month unless extended. I haven't yet, but will add highlighted notices of those P-1 assignments which are past due on the View Assignments page.
[/quote]When is "past due"? I would guess a month, but that's when they expire, not when we'd get a warning. I think two weeks after assignment would be a good time to highlight, what do the rest of you think? (Regarding why I reserved 100 a few days ago, this week is my spring break and lugging my desktop around didn't seem too appealing. :smile: I think it may be a bit more than a week of work, but then I don't think it's more than two weeks. Suggestion: As with TF, estimate how many days of P-1 we have reserved? That would be a good tool. (In fact, that's how I counted how much TF I needed for a week.)[QUOTE=chalsall;293336]
Lastly, just so people know, as Dubslow predicted, we currently have more P-1 work than we can handle, and are thus beginning to throw back to PrimeNet those canadidates we can't reasonable handle within about a week. The good news here is it seems there are many P-1 workers taking the work through PrimeNet rather than them going to LL workers.
[/QUOTE]
I would actually like to propose that you don't release any: At the moment, there are 20.8K candidates that need P-1; our current rate suggests [URL="http://www.wolframalpha.com/input/?i=20800%2F%2880+per+day%29"]we could clear that in 8 months[/URL]... okay, maybe we should release the higher expos. Keep in mind however that there are many more expos that we don't have that still need P-1, so I would not be worried in any way about overloading the non-GPU272 P-1 workers.
[QUOTE=chalsall;293336]In addition, to have the P-1 assignments appear as such on PrimeNet they will have to be transfered to another "state", and I don't want to lose any which have not already been maximally TFed.[/quote]
Why bother re-reserving them as P-1? As long as it's not reserved as LL, I say it's not worth the risk of losing it to PrimeNet if it already is listed as "Trial Factoring".


Otherwise, agreement!

[QUOTE=chalsall;293336]Also, P-1 assignments are now only available for candidates which have already been trial factored to 72 or more bits. [/QUOTE]

This would improve P-1 thruput, since P95 will be choosing lower bounds.