[RC5] Effect of CSC on RC5?
Basil A. Daoust
daoust at attglobal.net
Thu Nov 18 12:57:25 EST 1999
Well for me I've added computers to work on csc that were on SETI.
If you want to talk about a task with no end that has to be SETI.
So switching from RC5-64 to SETI seems to me like a step backwards.
It will be interesting to see csc stats like the rc5-stats where they
list everyone, groups, percent of keyspace completed etc...
To me it looks like dnet was not quiet ready to start this project
but though they better since someone else took up the challenge.
Someone suggested 9 days, before we new that csc would be slower than
rc5-64. But maybe this is still valid if more computers are assigned
to csc because of the potential short time line.
I have 10 wimpy computers all working on csc right now.
fastest is a lowly PII-300, slowest is a 486-66 which is brutal :-)
So in closing I say "SHOW ME THE STATS".
I tried to check to see how much work stopped on rc5 but the 17th stats
were still not posted when I checked.
> I'm wondering what the effect of the new CSC contest will be on RC5-64.
> Depending on how many folk switch over the CSC, we may see the RC5 keyrate
> drop by 50-90%. This would not be an issue if CSC were expected to run for a
> short time, but I get the impression that it could be months. There has been
> grumbling on the list already about the length of time RC5 is taking -
> basically, without an end in sight people can lose interest and wander off
> on to other projects (SETI etc).
> I don't want to start any wars over this, but are we (distributed) biting
> off more than we can chew? Or do we just consider RC5-64 a "background" task
> to only do when there is nothing else going on?
> 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