improving seti@home crunching

[jfw06013]

Hi,
I'm looking for tips on improving my average CPU times.
I'm running:
XP Pro
AMD Athalon Palamino 1800+
512 Mb ram

my stats so far are:

Results Received 855
Total CPU Time 4519 hr 00 min
Average CPU Time per work unit 5 hr 17 min 07.3 sec
Average results received per day 0.83
Last result returned: Fri May 6 14:44:40 2005 UTC
Registered on: Tue Jul 16 02:29:21 2002 UTC
View Registration Class
SETI@home user for: 2.810 years


Your rank: (based on current workunits received)
Your rank out of 5413627 total users is: 318315th place.
The number of users who have this rank: 241
You have completed more work units than 94.116% of our users.

User Certificates
Download 750 Workunit Certificate
Download 500 Workunit Certificate
Download 250 Workunit Certificate
Download 100 Workunit Certificate

Any ideas?

[Empty_5oul]

i dont know if running it through BOINC is any quicker ?? - i am not a SETI expert, someone else will help out though.

[Keith75]

I would move to boinc. Don't expect any faster times but it is going to be around alot longer and they are phasing out the old Seti at some point.

Keith

[Ototero]

The command line version of Seti run MUCH faster than the graphical version.

Boinc is too flakey for serious work :roll:

[Keith75]

Flakey? So harsh on the wonderful BOINC. I think I am the only one who really likes it. :roll:

[Empty_5oul]

elements f it are great but overall it never seems to piece together and work properly.

having 1 thing to control many sub-projects is a great idea however it has too many faults.

[vaughan]

As Ototero said - use the cmd line version not the pretty screensaver version. Also consider caching the work tasks. I have used SetiQueue successfully for a few years. For maximum daily output - don't run anything else. However, Seti Classic (not boinc) plays well with other projects.

[NeoGen]

Flakey? So harsh on the wonderful BOINC. I think I am the only one who really likes it. :roll:

Don't know if you're being sarcastic or not, but I really like BOINC too.
I must agree that it has too many flaws, I'd say maybe it should have been thought and tested more thoroughly before being released, but as I watch it grow and become a more mature and perfected DC platform I can't help to imagine how good it'll be in a couple of years from now... :D

[gamer007]

Same here. I like BOINC. Hopefully other projects will join in like Folding@Home.

I looked into http://distributedcomputing.info/ , theres some japanese projects using BOINC. I've also noticed some other projects using BOINC not shown on the official site. Could it be this projects aren't official projects?

[AMDave]

in answering jfw06013's SaH classic question...

are there opportunities to speed up his production?
Yes.

Obvious solution is to add a bit more RAM. Anything that reduces the likelihood of the O/S to read from the swapfile is a good thing.

Also, which version of the SaH client are you running?

As mentioned above, the CLI client is much faster, even in "verbose" mode.

The project still accepts work from 3.03 version of the client and we have demonstrated that the 3.08 client is slower. So if you have the older version of the command line client, I would move back to that. If you don't, PM me.

Other than that, the things you probably already know:
minimise the number of background services that are running
If you are not using the machine for gaming, you can try increasing the priority of the CLI client
maximise your up-time

BTW - if anyone still has the 3.03 client for Linux, please let me know.
I have misplaced both i386 and i686 binaries, so I haven't been able to do the Linux comparison of 3.08 and 3.03.