[RC5] keyrate stabilizing?

Ethan Daugherty etdaughe at vt.edu
Mon Oct 15 19:54:14 EDT 2001


Can we get one that says we are "29 an holding"?

Ethan


>We've tried using raw "unfiltered" statistics before (see CSC), and the
>response was not pretty.  Talk about conspiracy theories!  I have a hard
>time believing a stats page showing "OGR-24 is 274% complete" (or
>whatever it is) would be an improvement over what we have now.
>
>__
>Bruce Wilson <bwilson at distributed.net>
>PGP KeyID: 5430B995, http://www.toomuchblue.com/
>
>"Quidquid latine dictum sit, altum viditur."
>(Whatever is said in Latin sounds profound.)
>
>
>
>| -----Original Message-----
>| total stubs returned / total stubs * 100 = rough % done.
>|
>| It seems it would be much easier to give a rough percentage complete
>| figure.  Checking for duplicates and checking the 2nd pass to
>| ensure acuracy
>| of the returned data does indeed need to be done at some
>| stage,  but for a
>| simple 'we are about 74% done' figure, couldn't we just count
>| the number of
>| returned stubs?  Surely duplicate results are neglible in
>| comparision to
>| valid results and thus would not distort the rough figure too much.
>|
>| The other inaccuracy in this figure is that each stub
>| contains a different
>| number of nodes.  So a stub is not an accurate measure of
>| work done.  But
>| doesn't this average out in the long term, or does the
>| average number of
>| nodes per stub deviate as we move though the workspace?
>|
>|
>| --
>| To unsubscribe, send 'unsubscribe rc5' to
>| majordomo at lists.distributed.net
>| rc5-digest subscribers replace rc5 with rc5-digest
>|
>|
>
>--
>To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
>rc5-digest subscribers replace rc5 with rc5-digest

--
To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
rc5-digest subscribers replace rc5 with rc5-digest



More information about the rc5 mailing list