Interesting SETI Results

[Fardringle]

It has been known for some time that the command line client is faster than the GUI client, but here's an interesting example (for me) of how much of a difference there is...

I've been running the 3.0 GUI client on a P133 for a while now, and have been getting about 50-70 hour Work Unit times. Thanks to ColinP and Polo, I have now been able to set it up to run the CLI properly with SetiQ on my main system, and I am now seeing about 25 Hour WU times...

 

[lhampel]

Thanks for the info. (So that's how your staying ahead am me!!)

Maybe I should convert to the command line interface??

Current status:
Name (and URL) lhampel
Results Received 131 (up)
Total CPU Time 1426 hr 18 min
Average CPU Time per work unit 10 hr 53 min 16.2 sec (down)

 

[Fardringle]

I won't be ahead of you much longer at the rate you're going right now..

Current statistics:

Name (and URL): Fardringle
Results Received: 134
Average CPU Time per work unit: 14hr 12min 42.6sec


What systems are you running right now?
I have a K6-3+ 600, 1 Celeron 600, 2 P2-400's, 1 P2-350, 1 K6-2 500 and a P133...
(I'll be adding in a P3-800 as soon as the Finance Department gives me that check! ) <rubs hands greedily>

 

[lhampel]

Currently Seti is running on:
1-900Mhz Tbird ->3.0 GUI
1-1000Mhz Athlon ->3.0 GUI
1-650mhz P3 (laptop) ->Command Line 3.0

But...I'll be adding a few more systems to the group over the weekend.

 

[danzigrules]

well I guess I'm not doing to bad then with my little ole c2-600 @ 750 and my c-466 @ 525 then. Only a few a day behind you two. Wish them friends in Iowa would get their butts on line:|

Oh and the cli took about 2 hours off my c2

That's what I use on both

 

[Ken g6]

Fardringle, I'm guessing you never turned off the graphics in the GUI screensaver version of the client? They take up about half your CPU cycles, so that would explain your dramatic increase.

It's still not a bad idea to use the CLI client, though.

 

[Fardringle]

Actually, I had it set to always run, and to always run minimized - the only screensaver was Windows' Blank Screen...

 

[lhampel]

Fardringle, just a heads up...I've added another 1.3Ghz of Intel CPU power to my group.
Will be adding more to the group this weekend. (at least two)

 

[danzigrules]

Looks like I'm gonna get blown away

 

[JonL]

Fardringle,

What's up?

 

[Sukhoi]

Fardringle, are you really getting 25 hours/WU on a standard P133? I'm getting 33-34 hours/WU running the 2.04 GUI on a P133...I might have to switch to the 3.0 CLI tonight.

 

[Fardringle]

Well, the P133 is now about half-way through its second WU on the command line - 1st one was 25 hours, second one is at 51% at 14.3 hours..


Lhampel..I just added 2 P233's and another P2-400, and will be adding probably another P2-400 this weekend and a P3-800 sometime next week..


Hey Jon, get to work!

 

[lhampel]

Fardringle, well it's good to know your not going to sit back &amp; just let me win.

hmmmm...now if I could only remember where I put those quad P3-933 Xeon boards???

 

[Fardringle]

Quad Xeon system?
/me drools uncontrollably!


You could get 20+ WU's per day (or more) out of that one machine...that would be SWEET!!

 

[Ken g6]

And I'm getting 16 hours on my PII-400 with V3.0 CLi, where V2.4 took under 8 usually.

 

[Assimilator1]

Fardingle

The WU times from v3.0 vary by a much greater amount than v2.xx ,that 25 hr WU may of just been a fast 1 ,you'll get a better idea after about 10 WU's

 

[Fardringle]

ken_g6: Are you using the GUI client? If so, are you having the screensaver go to a blank screen? The PII-400 in my fleet averages about 10-11 hours with a 'Blank Screen' screensaver...

Assmilator: Yeah, I know, but with the GUI client I NEVER got a time lower than 50 hours whereas the first two WU's with the CLI are headed for an average of 26 1/2 hours...

 

[Fardringle]

Oops, double post..

 

[Ken g6]

As I posted above, I'm using the Command Line client. Blank screen couldn't hurt, but the likely problem is I'm gaming too much.

 

[Fardringle]

Yeah, gaming WOULD slow down your times..

(sorry, misread the line that said you were using the command line)

 

[lhampel]

Fardringle, I may have just passed you? Yeah @ work today we got 3 new servers (two with dual P3-933 xeon cpus &amp; over a Gig of PC133 ram)
&amp; Yes the thought of testing them out with seti command line did cross my mind...but it was only a thought.


lhampel
Results Received 139
Total CPU Time 1470 hr 42 min
Average CPU Time per work unit 10 hr 34 min 50.2 sec

 

[Sukhoi]

Why was it only a thought? Won't your boss let you run SETI on them?

 

[lhampel]

I'll find out.