Part of the puzzle is that yafu@home keeps multiple "tiers" of numbers available for various kinds of client computers (since it does no workunit=single composite progress saving or sharing, meaning a composite is factored all on one computer). Some clients have hardware that can do C140s in a reasonable time, some don't. That's why the table was extended to 2e6 in the first place, because collective progress was squeezing out the smaller clients who can't do C140s. At any rate, the upshot is that reservations are split among those two tiers. That middle quote of yours is I think very-long-term goals, for which the first quote is an intermediate short term goal for the smaller client tier, and is, I think, the current "release" target per the third quote (even though it says "mission", which was only previously used in the second quote). (Not sure what the specifics of the higher tier are, but it's fairly analogously similar to the smaller tier's intermediate rules I'm sure.)

OK quote one is the near-term reservation and quote two is the long-term goal. Is that correct?

I still don't get this whole releasing of downdrivers. So are they saying that they will not work on sequences that are below a certain size? In other words release the downdriver if it has gotten to too small of a size? If so what size? Was he implying 110?

I have noticed how slowly Yoyo seems to progress on sequences with a size of < 100; most of which are downdrivers. Perhaps they could release anything size < 100. Then we would have a ton of downdrivers to work on. :-)

This is just my gut feeling and I have no knowledge of yoyo's intentions. If he has too many "small number" sequences, then his server will become overflowed with many send/receive request because the numbers are being factored way too fast to keep up.

[QUOTE=gd_barnes;484492]OK quote one is the near-term reservation and quote two is the long-term goal. Is that correct?[/quote]

My best interpretation. Can't truly say if it's correct or not.

[QUOTE=gd_barnes;484492]
I still don't get this whole releasing of downdrivers. So are they saying that they will not work on sequences that are below a certain size? In other words release the downdriver if it has gotten to too small of a size? If so what size? Was he implying 110?
[/QUOTE]


Err.. actually I'm not sure what that means any more. Probably something about composite size versus sequence size, so even if it has recently developed a downdriver it may still have composites over the limit. At any rate I know the scripts have released several downdrivers already -- Batalov gobbled them up quickly.

OK let them release all the sequences with size < 100. :smile:

To make it clear.

Long term goal:
a) run all sequences < 1e6 to C144
b) run all sequences > 1e6 to C134

Short term currently I reserved:
for a) sequences < 110e3
for b) sequences between 1e6 and 1.4e6
When my queues runs low I will reserve a further bunch of sequences
for a) maybe up to 150e3
for b) up to 1.5e6 as mentioned earlier.

Independent of this I have currently reserved sequences outside of this range because of 2 reasons:
a) my reserve script was doing wrong and reserved too much, as mentioned here some days ago
b) at the beginning, as we enlarged the blue page to 2e6, I reserved just sequences with smallest size, means also sequences outside above ranges. It was blamed in this forum, that I catch all small sizes. So, I changed to above missions and keep the remaining open for others.
Some of those sequences I still own. Those will be released and those might be downdriver.

Drop 1809480 (2^2*7, ECMed C122)
Drop 1844040 (2*3*ECMed C116)

Taking 1506648 1606554

Taking 1546272

Update 1679436 1828680 1795536 1711638
Reserving 1946946 1989288 1877280

[QUOTE=yoyo;484517]
Long term goal:
a) run all sequences < 1e6 to C144
b) run all sequences > 1e6 to C134
[/QUOTE]

Can we assume these sequences has some ECM work before releasing?