If you would rather run Seti over RC5 then I suggest you run both. I would rather have my CPUs running Seti because of the underlying science associated with it but I have noticed that if I run RC5 and Seti together then Seti gets about 99.5% of all of the processor time. You ask, what good is that? Well, first, those CPU cycles that Seti doesn't use are not wasted and more importantly when the Seti server is down as it seemed to be this morning, my CPUs weren't just sitting idle.
So if you like Seti then run both Seti and RC5... It won't hurt your Seti production and at the same time you can make a small contribution to RC5.
Just my $0.02
So if you like Seti then run both Seti and RC5... It won't hurt your Seti production and at the same time you can make a small contribution to RC5.
Just my $0.02