I just set my SETI to run with screen saver, and have RC5 running when I'm using the comp... so essentially they're now taking turns.Originally posted by: Ken_g6
On Win9x this would tend to result in SETI taking all the cycles, leaving RC5 with only a few percent. But that few percent will tend to suck memory bandwidth from SETI. It's generally a lose/lose situation.
On other OSes they may be more balanced, but RC5 will still suck memory bandwidth from SETI. Best to run one project per processor.
Note that the exception is dual processors. RC5 sits in one processor's cache, so SETI gets all the memory bandwidth on the other - it's better than running two instances of SETI.
I know... it took well over an hour to do 15% with the GUI client.. lol. An entire WU only took 4-5 hours with the commandline client. It's more for the eyecandy, the GUI one. But whatever... it will make no difference, I run seti and rc5 on ONE computer, not 500 diff comps... so it won't make much of a diff which client I use.Originally posted by: Ken_g6
That sort of works.But the SETI screen saver is ~25% slower than the SETI command-line client. It seems like someone once produced a screen saver that ran another program; that might help.
