Newer milestone thread

[chalsall]

Originally Posted by Madpoo

That's some inside baseball stuff there, but for everyone else, let it be known that even under the grandfathered rules, there are still some allowances made where expiration won't happen until those exponents are actually going to be reassigned to someone else in the short term. Otherwise that computer gets to hang on and hopefully get it done.

But... That still doesn't explain why 33944569 has not been recycled.

This is not a grandfathered assignment, nor has any work been done on it, nor has it even been checked in recently. Why has it not been recycled? According to the stated assignment rules, it should have been.

All I'm asking is that what is promised is actually what is done. Or, alternatively, that what is actually done is communally known.

[ATH]

Originally Posted by chalsall

But... That still doesn't explain why 33944569 has not been recycled.

Just an idea: Maybe 108 days ago 33.9M was in cat 3 so it has 180 days to start? I assume the category at assignment counts and not the category the exponent moves to after assignment?

[chalsall]

Originally Posted by ATH

Just an idea: Maybe 108 days ago 33.9M was in cat 3 so it has 180 days to start? I assume the category at assignment counts and not the category the exponent moves to after assignment?

Possible, but I seriously doubt it.

Happy to be proven wrong (I don't currently spider the thresholds page, so I can't say for sure).

[Prime95]

Originally Posted by chalsall

Possible, but I seriously doubt it.

I doubted it too, but the cat 3 threshold on 11-08 was 33944558.

Maybe we need a web page that displays that info....

[chalsall]

Originally Posted by Prime95

I doubted it too, but the cat 3 threshold on 11-08 was 33944558.

Maybe we need a web page that displays that info....

Thanks George! My bad.

A web page showing that data would be helpful. And, perhaps, we should consider increasing the boundries for the lower categories for DCs by a little bit? Clearly the Cat 1 workers are eating quickly!

[Prime95]

I added the date feature to the assignment rules page. You have to know the hidden parameter to use the feature:


http://www.mersenne.org/thresholds/?dt=2014-11-09

[TheMawn]

(Slate this comment for removal)

[chalsall]

Originally Posted by Prime95

I added the date feature to the assignment rules page. You have to know the hidden parameter to use the feature:

Thanks George! Very helpful for the OCDs amongst us who don't have access to the raw DB.

May I suggest we start a discussion (either here, or on the original "new assignment rules" thread) about increasing the deltas on the different ranges for DC? I'd initially suggest something like Cat 1: 5000, Cat 2: 15000, Cat 3: 50000.

The whole point of the new rules was to lessen the motivation for "poaching". Clearly this and other examples shows that Cat 3s may slide into the Cat 1 range well before the candidates are soon due for recycling, thus unintentionally creating a bottleneck.

Actually, taken at the extreme, there could be an interesting self reinforcing situation wherein almost the entire Cat 1 range is actually old Cat 2s and 3s, while the fast / dedicated machines mostly clear out Cat 2s and 3s. We should really aim for a balance such that if a candidate moves into Cat 1 that it's just about to be recycled by the system.

Thoughts?

[Mark Rose]

I think that's a brilliant idea.

[Anonuser]

Originally Posted by chalsall

Thanks George! Very helpful for the OCDs amongst us who don't have access to the raw DB.

May I suggest we start a discussion (either here, or on the original "new assignment rules" thread) about increasing the deltas on the different ranges for DC? I'd initially suggest something like Cat 1: 5000, Cat 2: 15000, Cat 3: 50000.

The whole point of the new rules was to lessen the motivation for "poaching". Clearly this and other examples shows that Cat 3s may slide into the Cat 1 range well before the candidates are soon due for recycling, thus unintentionally creating a bottleneck.

Actually, taken at the extreme, there could be an interesting self reinforcing situation wherein almost the entire Cat 1 range is actually old Cat 2s and 3s, while the fast / dedicated machines mostly clear out Cat 2s and 3s. We should really aim for a balance such that if a candidate moves into Cat 1 that it's just about to be recycled by the system.

Thoughts?

A useful step could be to recycle category 3 (and category 4) assignments that moved into category 1, and that have not been started. (Of course after communication with the server to make sure that no work has been done, and not immediately after they move into category 1).

[Prime95]

Originally Posted by chalsall

May I suggest we start a discussion (either here, or on the original "new assignment rules" thread) about increasing the deltas on the different ranges for DC? I'd initially suggest something like Cat 1: 5000, Cat 2: 15000, Cat 3: 50000.

The whole point of the new rules was to lessen the motivation for "poaching". Clearly this and other examples shows that Cat 3s may slide into the Cat 1 range well before the candidates are soon due for recycling, thus unintentionally creating a bottleneck.

Actually, taken at the extreme, there could be an interesting self reinforcing situation wherein almost the entire Cat 1 range is actually old Cat 2s and 3s, while the fast / dedicated machines mostly clear out Cat 2s and 3s. We should really aim for a balance such that if a candidate moves into Cat 1 that it's just about to be recycled by the system.

Thoughts?

Good idea.

Since cat 2 users have 100 days and cat 1 users have 60 days, I don't think the extra 40 days will cause much poaching concerns. Cat 2 is for users with slower but still relevant computers. We don't want to make them feel unwanted by denying them access to too many of the smallest exponents (or maybe I worry too much?). Recommend first number be moved to 2000 or 2500.

Cat 3 with the 240 day expiration will unfortunately present a poaching target when it slips into cat 1 territory. Change the second crossover to 15000 or 20000 (or more?).

Cat 4? Not sure if that needs changing or not. I thought we chose 40000 because we had completing 40000 DCs a year.


LL testing. We have the opposite problem, big swaths of unclaimed exponents. Change from 5000/15000 to 2500/7500??? If curtisc ever activates the trusted user bit, then we have some big adjustments to make!