Hi Robert,
[Robert van der Peijl:]
> We might not need a special version of prime95.
> How about if the _PrimeNet server_ itself only issue expired
> exponents to "power"-users?
> If that is a real possibility, perhaps Scott Kurowski could
> look into that?
I would instead recommend a broader strategy that expires exponents based
upon the assignment age (days run) and current iteration at null (not
started), perhaps at 60 days age. Did someone already suggest that? This
will have the system effect of generally causing machines that grab and hold
excess exponents to lose smaller exponents to new or more productive
machines, while making up for those losses by grabbing fewer, ever larger
exponents. This would happen in addition to the current automatic
expiration process.
The risk that a machine actually started a long-held exponent before
contacting the server to learn it had been reassigned is somewhat greater.
The result would be slightly more frequent 'opportunistic' double-check
passes as the machine forges along to complete the then-redundant test,
probably after the reassignment machine finishes. Maybe that's a good
thing.
George Woltman manages the server's individual exponent and range
assignments from time to time. If overriding a 'squatter' is important
enough, he could do so manually. However, if server changes are necessary,
we defer to him for those requirements.
(If there are replies, please cc me directly since I receive only the
Mersenne list digests.)
regards,
scott kurowski
Entropia, Inc.
San Diego, California
P.S. if there are any GIMPS folks on this list nearby, I'll treat lunch or
beers... I left Ernst and Luke in Silicon Valley. :-(
_________________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
