Features request?

[Madpoo]

Originally Posted by chalsall

Having the deltas allow us to make an informed decision as to how many we can take to 75, and how many we should only take to 74. My goal is to not have assigned for LL'ing anything not at at least 75 bits above 65M. GPU72 will "recapture" anything released for P-1 at below 75 bits for final TF'ing, assuming a factor isn't found by the P-1 run of course.

I know this is going to show my ignorance of the setup, but when GPU72 reserves exponents to take up to 75 (in that range, for example), does it actually hold on to them until it reaches 75 then? So if someone gets that work and only takes it up to 74 bits but doesn't want to go to 75, that exponent will sit in the GPU72 reservations unless action is taken to unreserve it to feed the P-1 beasts?

I don't know if this would be a better or worse situation, but maybe GPU72 could reserve exponents to be done a bit level at a time instead of (optimistically?) taking a bunch and going all the way from like 72 to 75 in one go. Would it be better for this situation to take a wide range and first get them up to 73, then 74, then 75, sending them back to Primenet between each bit level being complete?

In a perfect world it wouldn't matter if a bunch of workers took a batch and went through them one exponent at a time, taking each one all the way to 75, then returning it. But given the circumstances, it seems like maybe the better option is to take at least the exponents in the leading P-1 edge and only do a single bit more at a time rather than going for the full 75 at once.

Again, it may be my total lack of comprehension on what's happening under the hood, so please disregard if I'm way off base. It wouldn't be the first time.

[chalsall]

Originally Posted by Madpoo

Again, it may be my total lack of comprehension on what's happening under the hood, so please disregard if I'm way off base. It wouldn't be the first time.

Primenet currently hands out candidates for LL'ing based on the P-1'ed status first. P-1 done is assigned before no P-1 done, then the lowest candidates without P-1 done, grouped by the status %1M.

This is further complicated by the four different Categories for DC and LL.

It can be argued that GPU72 is actually "starving" Primenet such that only those candidates appropriately TF'ed / P-M'ed are available.

[storm5510]

Originally Posted by chalsall

...It can be argued that GPU72 is actually "starving" Primenet such that only those candidates appropriately TF'ed / P-M'ed are available.

This could be the reason why my assignments are one bit higher on each side than what I have in the config file. I do not have a problem with this at all. Just a curiosity .

[chalsall]

Originally Posted by storm5510

Just a curiosity .

I'm not clear what you're asking / stating?