Forums | MacLife

A third dock app that is available on the seti site is called Seti Mania...
http://setiathome.ssl.berkeley.edu/links_addons.html
...its decent does a few other functions like keeps track of your history and group standing as well as a few others.......

The major problem with it is it is extremely difficult to understand and configure unless you even moderately proficient with french.
it does somewhat attempt to translate but this is inconsistant at best, and any "read me" documentation in english is non-existant.
So like I said if you know French this is a good option, if you don't then that means I just waisted your time by even telling you that it exists. 

If thats the case, Sorry.

This will run SETI faster than the graphical version, right?

Theres never a guarantee but it should help you get your WU's done a lot quicker profided that you dont run a lot of apps at the same time... I got about a 20% decrease in time per WU , meaning I used to be doing one in about 12 - 15 hours and now I am getting between 9 - 11 hours.....
of course this isnt real scientific yet I havent been running it that long... but so far it seems to work well.

Hmm.  I would have thought the CLI version would be faster as well.  Not so here.  I had the GUI seti client running for 5 hours and got 20% completed in screensaver mode (I log out and go to a hot corner).  Using the cli from the terminal, after 5 hours I have 7% done.

Weird.

Jeff

I've said it before and I'll say it again. SETI's client scales almost perfectly with MHz, and is pretty FPU depedent.

Based on most FPU benchmarks from when the G4s came out, a G4 should give about 5% faster crunch times than a same-clocked G3, but individual units vary as much as 25% on the same CPU, so it's statistically insignificant.

The only time things like bus speed or memory latency have much of an effect on crunch times is when they are incredibly bad. An iMac 233 will crunch a unit in 30 hours, but a 6100 with a 240 MHz G3 upgrade will take about 45 hours.

With the 3.03 client, this is what I get:
350 MHz = 20 hours average (MacOS 9 GUI app w/ windowshade or MacOSX CLI, G4/350, PMac 7300)
500 MHz = 16 Hours average (MacOS 9 GUI app w/ windowshade, Sawtooth G4/500)
700 MHz = 9 hours average (MacOS X CLI, eMac)
700 MHz = 9 hours average (WinNT CLI, Duron)
1 GHz = 5.9 hours average (WinNT CLI, T-Bird Athlon)
2 GHz = 3.2 hours average (WinNT CLI, T-Bred Athlon)

There is a slight slacking off between the 1 GHz and 2 GHz points, I would assume because I used DDR266 with both systems, and it's holding the 2 GHz Athlon back a bit. OCing the FSB to 2x140 MHz drops the crunch times for the 2 GHZ Athlon into the 2.8 hour range, which is entirely out of proportion to the 5% clockspeed increase. I need some PC2700 so I can up my FSB to the 166 my mobo supports... *drool*

What's really telling is that the eMac 700 and my little Bro's 700 MHz Duron turned in identical crunch times. Given that they are both SDR systems with a 100 MHz system bus (though the Duron is supposedly a 200MHz-equiv. DDR FSB) this would seem to indicate that SETI is completely clock-bound, regardless of the obscene degree of difference between the PPC 7450 and Duron designs.
So, in short, it doesn't matter what kind of computer you have, or what 'tricks' with ramdisks you try. MHz = Faster SETI@Home. Period.

Is there a speed hit in other apps when running the CLI SETI@home client? Keep in mind, I'm on a G4/400.