[RC5] Problem with buffer limmits.
gsimms at icon.co.za
Wed Oct 27 15:15:39 EDT 1999
Didn't realise there was a buffer limit..
I've noticed in the rc5des v2.7112.444-CTR-99092203 client for Win32
(Windows 4.10) that running a benchmark test no longer suggests an
appropriate block size or buffer values for a 3 day period.
I relied on this feature to choose the most appropriate settings for the
clients I used.. without it, I fear running out of blocks or using the
wrong blocksize :(
I was thinking about this and realised the perproxy folk had similar
problems.. The solution in the proxies is to add some sort of "artificial
intelligence" that calculates or estimates rather how many blocks to fetch
based on what is requested. I think it would be very useful to implement
this feature into the client, with advanced users naturally being able to
override it if they need to.
It would be useful for beginners who don't understand the complexities of
buffer and block sizes, allowing them to install and forget just about. The
client would then decide how many buffers to get based on how often it is
able to connect to the server and how often it runs. This would avoid
duping random blocks, and increase reliability.
----- Original Message -----
From: William Scott Lockwood III <scottlockwood at hotmail.com>
To: <rc5 at lists.distributed.net>
Sent: Saturday, October 23, 1999 3:29 PM
Subject: [RC5] Problem with buffer limmits.
> Are we going to do something about these buffer limits anytime soon?
> I'm leaving for the weekend - My new Athlon 500 will run out of blocks in
> about 24 hours, and will crunch lots of random blocks after that - some of
> which I may not get credit for if lots of other people have generated the
> random blocks. This has happened to me before. I once got an e-mail from
> D.Net about it. They seemed to think I was spamming the keyserver - NOT!
> Haven't we proved yet that with faster and faster CPU's, the block limits
> plain don't make sense? We should AT LEAST double them for people with
> PII/III and Athlon CPU's!
> 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