[RC5] keys stuck in a loop??

Mike Henry dnetc at mrtickle.demon.co.uk
Fri Sep 14 22:58:27 EDT 2001

On Fri, 14 Sep 2001 12:14:24 -0400, waldo kitty wrote:

>Bruce Wilson wrote:
>i'm running a perproxy here servicing a dozen machines on the internal
>network and possibly a few from outside... the reason i have them
>configured in such a "short stack" is that i highly dislike waiting
>hours or days to find out that something is wrong... that's also why i
>dumped OGR processing... these machines range from 486-33 to celeron 300
>with at least one amd k6-450 in the bunch...
>also, i very much disliked going to the stats pages and seeing the
>entries "bouncing around" as keys were dumped in in large bulks every
>other day or so... with the current configuration, the graph is very
>smooth instead of hugely spikey and i also get a better idea of my daily
>average unit processing without having to do any math...

How lazy.

>> Connecting every 20 minutes is wasteful in other ways, too.  By
>> connecting 72 times a day, you are putting an unnecessary load on our
>> network, and reducing your effective keyrate.
>that's why i have them configured to have at least one key in the buffer
>at all times... one waiting, one being processed... the background
>threads should take care of sending completed and receiving new units
>while the client handled that second key that was waiting...

How utterly selfish. Never mind the excessive load you're placing on
distributed.net - as long as you have a nice pretty graph and don't have
to do any maths yourself, that's all you care about?

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