• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

These SETI numbers don't seem right.... am I doing something wrong?

N

notfred

Lifer
Last night, I started the GUI client for SETI on three different machines. An Athlon XP 1600+ running windows 2000, a PowerPC G3 700mhz running Mac OS X, and a Pentuim 3 500mhz running redhat linux 8.0.

Now, I came out this morning and looked at them, and the athlon shows 31% complete, with 10 hours and 12min of CPU time. The Mac shows 46% complete, with 11 hours, 12 minutes of CPU time, and the P3 shows 39% complete, with only 4 hours 56 minutes of CPU time.

Aren't these numbers really high? Why is the slowest macine showing the best progress? Am I doing something wrong? I don't have a lot of SETI experience here....
 
There are a few things I would check.

Check the power saving options and make sure that the option "turn off hard disks" is set to "never".

Turn off all screen savers.

Check the BIOS and set the CAS Latency to 2.

Uninstall the GUI and install the CLI unsing these instructions.

Doing those things will get you the fastest setup possible for your machines.
 
Originally posted by: notfred
I wish the CLI client at least gave a progress meter.
Click to expand...
Use Seti Driver or Seti Spy. Seti driver is probably your best bet so that you could build up a small cache of work units in case Berkeley goes down like it has today.

 
Originally posted by: minendo
Originally posted by: notfred
I wish the CLI client at least gave a progress meter.
Click to expand...
Use Seti Driver or Seti Spy. Seti driver is probably your best bet so that you could build up a small cache of work units in case Berkeley goes down like it has today.
Click to expand...

got it, but I can't downlaod the CLI client, seeing as how the server is down.
 
If you just want to check the status, without the other stuff, you could use SETIWATCH as well. I used it when I had SETIDRIVER installed as a service.

Using the locations tab, I added a location to SETIWATCH for each cached WU, assigned each WU a different color. 🙂

Then I could tell exactly which WU was being processed, and the progress. 🙂

SETIWATCH works well without SETIDRIVER too. 🙂

Just giving you another option. 🙂

Get SETIWATCH here!
 
SETIWatch is also an awesome program for monitoring multiple computers over a network. I still use it to see if the computers are turned on even though I'm not running SETI on any of them anymore.🙂

To use SETIWatch in conjunction with SETIDriver you just have to select the create setilog.csv option in SETIDriver. SETIWatch doesn't have to be open all the time just open it up when you want to check on your clients or view your stats.
 
Preformance for the Athlon and Pentium is pretty even. Your 1600+ should do a WU in 4:15, the P3 in 10:30, and I'm not sure about the Mac.
 
Yep, SetiWatch can also point out possible problems on a machine. If you see a client that's got an abnormally high WU time it's usually an indication there's an app hung and the PC needs restarted. 🙂
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top