>> That is to say when
>> one computer finishes to X%, it reports its 64-bit residue to primenet, and
>> waits for the second computer working on the same LL test to do the same.
>> Until the other (slower) computer reports in, the (faster) computer works on
>> another exponent.
> Not at all. The first-time check goes its way, but reporting
>partial residues to coordinator / primenet from time to time. Later,
>often when first LLTest was finished long time ago, somebody
>receives:
>Double-Check:
>M23780981,64,863FF87,678676AA,FF637BC,[...],CRC:9923FDA.
This scheme makes almost no sense for normal double checking. This is becuase
it would save *no* time at all. Think about it, even if you identify that an
error ocurred in the second week of a 3-month test, you still have to run it
to completion, and a third test must also be run. (So 3 LL tests must still
be run if an error ocurrs).
> This schema makes possible simultaneous checking,
> though. But the start-stop mechanism you describe has little
> sense.
The method that you describe would only allow simultanious checking if
the computers were of equal speed, or if one kept working on the same
exponent, and the other computer kept getting further behind. The scheme
that I described (and Brian thought up) would allow the computers to run
at the same exponent/time, while still keeping busy.
Sorry about my bad english, and it's even my first language!
-Lucas
_________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
