How fast do you process SETI WU's?

[adams]

And what type of setup are you using?

I'm curious to see how much of a difference different types of clients/processors/ram/os and anything else make.

I'm currently running a Duron 600@909, with 128MB Crucial RAM set at Cas 2(I think) with Win2K and the 3.0 command line client. My WU's take about 4.5-5.5 hours.

Thanks

Adam

 

[Fardringle]

My K6-3+ 450@600 on an EPOX MVP3G5 with 128MB of PC100 CAS2 RAM averages about 10-10.5 hours..

 

[pandaflux]

My Celeron 533A @ 896 w/256 ram @ 112fsb 2-2-2 on a abit BH6 can do a work unit in just under 4 hours. Thats with WIN ME and the 3.0 command line client along with just about all the tweaks i could perform. good old BX still sittin pretty with me.

 

[mechBgon]

I am using the CLI 3.0 on a Duron at 840MHz, 105MHz fsb with PC133@138MHz, CAS 2-2-2, and Win98SE. I run SETISpy along with the client and my last 10 WUs average out to 4.74 hours per WU, which includes some Web browsing. Pretty similar to your system there...

The other system that runs SETI here is a dual-Celeron system at 552MHz per processor, with the RAM running at 92MHz 2-2-2. I run the CLI 3.0 client on CPU 1, and SETISpy and Dnet's OGR client on CPU 0. That system is averaging 6.54 hours per WU in that setup, despite my using the system for IRC chat in the evenings. Adding SETI and a second instance of SETISpy bogs the efficiency down considerably, with WUs taking about 10 to 12 hours.

 

[SilverBack]

1.25 GHz Tbird does 3.5 hours per WU.
1.0 GHZ TBird does 4.3 hours per WU.
Duron 800 5.0 hours per WU.
P3 800 5.5 hours per WU.
Athlon 700 6.2 hours per WU.

 

[rleach2]

P3 650@917 on a BE6 II with 192MB PC133 RAM @ CAS3(RAM can't handle the high Bus speed at CAS2) averages about 3h39m12s per WU.

 

[blade47]

I'll just list my fastest machine.

P3-500e @ 620mhz (5*124mhz fsb)
Abit BX6rev2.0
128mb Cas3 ram
WinMe
commandline client v3.0
5.5 hours is the average for my last 10 wu's

I plan on getting some PC-150 cas2 ram soon and jacking it up to get some decent times.

 

[Sukhoi]

C433, 192 MB PC66 CAS2 RAM, and I'm getting 8-10 hours/WU.

 

[Assimilator1]

Celeron 366 @ 550 ,192 Mb CAS 2,Win 95c ,CLi v3.0 ,average 7hrs/WU
Celeron 300A @ 464 ,128 Mb CAS2,Win 95c,Cli v3.0 ,average 8hrs/WU
PII 350 @ 392,256 Mb CAS2,Win 98 ,GUI v2.04 ,average 9hrs/WU
PII 333 @ 374 ,128 Mb CAS3 ,Win2k,GUI v2.04 ,average 12hrs/WU
K6-2 550 ,128 Mb ,Win 98 ,GUI v2.04 average 26 hrs!
K6 200 ,64Mb CAS2 ,Win 98SE lite,GUI v2.04 26 hrs
PIII 500 ,unknown specs ,GUI v2.04 ,about 8.5 hrs/WU
Athlon 700 ,128Mb CAS2(133MHz) ,Win 95c,GUI v3.0 ,Average 6.5hrs/WU

Thats most of them

 

[ColinP]

Ass1..

What's up with your K6-550 at 26 hours ????

My K6-2-500 at 525 {5x105} 512k L2 mobo cache running RedHat 7.0 averages around 14hours,
with these easy WUs it's doing them in 11.5 hours !!!!!!!

Even my K6-2-400 running Win2000 does them in 17 hours usually...

Have you got a problem with that machine ???

Col

 

[Mp3lova2k]

PIII 800, Win2K-sp1, 128MB PC100 CL3 running with 4h30 to 5h/unit

 

[SETIdude]

I would think that his high WU times on that machine are due to the GUI client that he's using and you're not. Just a guess

 

[Robor]

I've got too many boxes to list but my best/primary box is:

Asus CUSL2 / P3-700@1014 / 256MB CAS222 / Win98SE that averages about 3hr 30min. Best time other than WU's that finish in a few minutes is 2:58:48. I've had 5 WU's complete in under 3hr's between 12/09/00 and today. Gotta love these easy WU's!

Rob

 

[Orange Kid]

P3-500 WIN_ME 256/meg ram 6h17m42s
P2-350 WIN_98 128/meg ram 8h59m58s
P2-233 WIN_98 64/meg ram 12h6m32s
K6-2-350 WIN_2K 92/meg ram 15h27m47s

These times are from setiQ--118 units sent through.
Nothing over-clocked all cas2 memory timings.
All running CLI 3.0---Use setiWatch to monitor.

 

[Nighthawk69]

~4hrs. Give or take 30 mins depending on the WU.

CLI 3.0

 

[The_One]

I/we (me+d1) got a few machines that do WUs in about 3 hrs, will get back with details and a list of the others (there's a few).

t1

 

[BadThad]

I have a huge fleet, but my fastest PC is my main one at home:

P3700E@868MHz
512MB generic RAM @ 2-2-2
Asus P3V4X (124fsb)
98SE
CLI v3.0 with SETI Driver

average of 66 wu's = 4 hr 39 min (this includes web surfing and general use 30% of the time)

High= 7 hr 42 min (man, what a stat killer!)
Low = 3hr 37 min (excluding junk result of 13 min)

 

[Binky]

P3-700@933 on a CUSL2, 256MB@2-2-2, most WU's come in at about 3:10.

At CAS3, the time increases to about 4:15.

 

[lane42]

wow, I didnt know a p-3 933 was faster then a 1.2 TBIRD.
Always learning something new.

 

[GoSharks]

<< P3-700@933 on a CUSL2, 256MB@2-2-2, most WU's come in at about 3:10. >>



damn, need to get faster ram

p3700@933
Abit SL6
192 pc100@100mhz 2-2-2-5

ave time is 4:37 running win2k sp1, v3 cli, and me brosing the web.

 

[Binky]

Those damned &quot;low angle WU's&quot; take about 4:15 at Cas2, or about 25% more time. The Intel 815 chipset is also a big boost to the seti times. My old VIA based motherboard (Aopen AX63pro) was not as fast.

Additional info: WinME, 3.0 CLI, fast 7200rpm IDE drives

Thank you compuwiz for this kick-ass P3-700!!!

 

[Stallion]

My 700@933, 128mg mushkin PC133 CAS2 has been doing units in 3:10 (high angle) to 4:20 ( low angle).

550 Katmai, 128 mg corsair PC100 CAS2 does then in 5:30(high) to 7:30 (low angle).

 

[Assimilator1]

Binky

I was wondering where your increased output came from ,how long have you had that?

 

[Binky]

It's my personal machine and it is always changing. The current p3-700@933 on the CUSL2 has only been running for about 2 months. Before that it was an P3600@800 on a VIA board. Once I saw how fast the WU's were getting cranked out with the new setup I just had to start leaving it on 24/7. I can't let Hellburner take my spot easily!

 

[Assimilator1]

Binky

You've only just left it going 24/7!?:Q ,I did that 5 months after joining the team,it was only supposed to be for a month or so too! ,that was 6 months ago! .
BTW want a little help?

ColinP

I've had this problem before with previous ship I had ,that was also a K6-2 but a 500.It did Wu's in around the same time ,about 26 hrs.This is with GUI v2.04 (screen blank in 1min).
I had a thread about it some time back ,me Hymy &amp; a few others came to the conclusion that the poor times were due partly to having a 512k cache (compared to 1Mb) ,the chipset latnecies,CAS3 RAM &amp; for some odd reason many K6-2's just run the GUI version very slowly.They fair much better at the CLi version.Unfortunatly both that K6-2 &amp; the 550 are remote ships (deep space assignments) &amp; putting the CLi on could mean days of lost production if they forget to turn it on.
My little brother's (THE TERMINATOR) K6-2 @ 375 (on an Intel TX chipset Asus m/brd) using CLi v3.0 seems to be averaging about 18hrs/WU! ,thats on Win 95b.The K6-2 500 &amp; 550 are on Win 98.
Forgot to mention that the K6-2 500 is no longer crunching.
The owner of the K6-2 550 also has a Athlon 750(?) and is quite happy to add that to my fleet when he brings it home .along with a PIII .The bad news for me is that he's rather interested in it himself &amp; will probably create his own account soon ,he seemed quite happy about the idea of joining TA though .Watch this space........