On Tue, Jun 15, 1999 at 10:01:04AM -0700, Mersenne Digest wrote:
>This is why George no longer supports
>it in the CPU check boxes.  I wonder how long it will be before he drops
>486's.

Hopefully there will be a while to -- my 486s are all performing excellent
factoring.

---snip---

>Could I respectfully suggest that, in future, list members flame 
>each other in private (at any rate, after they've posted their views 
>once). I don't much like the smell of toasting flesh.

(As always, I have to follow Brian in everything...) Quite sensible.

---snip---

>Scott, do you have a time estimate for that when extrapolating the
>current growth?

Extrapolation is dangerous. If the growth continues, the number of
people on the Internet will cross the world population in only 10-15
years.

---snip---

>  D           D     F     -    prefer double-check, fall back is factoring
>  D+F         D     F     -    ditto
>  D+P         D     P     F    etc.
>  D+P+F       D     P     F

And if `most sense' is applied? Will a PII only get LL assignments, or
nothing? (Currently, this isn't a big problem, though.)

>transaction object.  This is where we set rules like, 'give all v17 clients
>double-checking work'

Hmmmm, I thought they were bugged?

>However, when I set up Prime95, I
>indicated that it was only going to be running 6 hours per day.  As
>expected, the machine originally requested factoring assignments.  Also as
>expected, since it was really running 24x7, it raced through the factoring
>assignments much more quickly than PrimeNet expected.  After 4 or 5
>factoring assignments, PrimeNet started assigning double-checking to the
>machine.  Now it's going quickly through double-checking assignments.
>Last night, I noticed that the PrimeNet server assigned this machine an LL
>test of an exponent in the 7,400,000+ range!  My question is, does the
>PrimeNet server look at the actual speed a machine is achieving to
>determine what it should assign?

I would guess what you've encountered is George's `rolling average' function.
If your actual speed is exactly the same as the expected speed, your
rolling average is 1000. If it is twice the expected speed, you get 2000 etc.
(Mine is 1432, you can see yours in the `local.ini' file.) It looks like
what has happened is that Prime95 multiplied your expected speed
(MHz*hrs/24) by RollingAverage/1000, and (correctly) reported this number
to the PrimeNet server, which in turn based its decision on this information.
I wasn't aware that the rolling average was used for this, but it looks like
it is. (It is also used for correcting the `exponent finished' estimates.)
The reason you got factoring (and later double-checking) assignments in the
beginning was probably that the rolling average function needed some time to
adjust.

Congratulations to George and Scott, who seem to have thought of
_everything_ :-)

---snip---

>Likewise, if we see S hit zero at some intermediary point

If we see S hit zero, _all_ the next number will be -2, and _all_ the
remaining ones will be 2. (0 squared minus 2 is -2, -2 squared (4) minus 2
is 2, 2 squared (4) minus 2 is two, and there is your endless loop.) Or?
(From what I've read on this list, there are two different series of LL
numbers. Perhaps I'm just way off here.)

/* Steinar */
________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm

Reply via email to