Which version of the SETI program do you have? Is it version 3.0, version 3.03, or an older one?
For your system, a good typical workunit time with the latest version (3.03) would be 7 to 8 hours (the workunits themselves are not all the same). The older version 3.0 client had completion times in the 5-hour area, for reasons I'll skip over here. SETI is sensitive to memory bandwidth and therefore runs at its best with no other programs running. If you're running RC5 at the same time, that is probably part of the reason it's taking so long. If you have the SETI screensaver graphics enabled, your times may be
doubled! In fact, the fastest version of the SETI client is the CLI version (a simple text-based DOS box version).
It sounds like your primary interest is stability testing, and for that I think that SETI
without RC5 will make your CPU work harder, since the CPU will be going full-speed on SETI. SETI makes my RAM get hot, so you can be pretty sure it's pushing the whole memory bus quite hard. If you want to run SETI in the long term, check out the "Team AnandTech" link in my sig, we have a good SETI team.
Here's a link to the CLI version and you will probably want to run it with
SETISpy so you can look at the setispy.log file in WordPad and see how long the work units took to complete.
As for RC5, the packets themselves may contain anywhere from 1 to 32 work units each. RC5 is not very touchy about other programs, it will just claim whatever CPU cycles are left over by other applications and use them. You can look for lines like these to see what the output is:
[Jan 28 09:23:26 UTC] RC5: Summary: 222 packets (5566.00 stats units)
5.13:55:36.31 - [3,092,710keys/s]
and compare it with your results in
the Team AnandTech speed page, which will calculate your ideal RC5 output for you. Just put your CPU MHz in the box.
edit: you can enable screen blanking on the GUI version of SETI in order to increase its efficiency too. The CLI version is still faster but enabling screen blanking after 1 minute will help a lot too. SETISpy gives all kinds of good info and I think it's worth downloading it and trying the CLI version.