Hmm Ok, I give, how are some of you guys breaking 5 hours in S@H?

[SilverBack]

Here is how I'm doing:
Averages:

6h46m01s..Helen..........P3 803 oc'd P3 733 PC133 ram CAS 3 at 146MHz ( wife's pc )
5h21m49s..Achilles.......Duron 900 oc'd Duron 600 PC133 CAS2
7h50m01s..Ajax............Athlon 800 oc'd 700 ( 64 mb PC100 Cas 2, limiting factor )
5h04m03s..Odysseus...TBird 1023MHz oc'd 800MHz PC133 CAS2

I see some of you guys are saying that you are near 4? ARGH!!! Where are you at NASA?:Q

LOL

 

[TuffGuy]

check my sig... i'm running kinda slow right now though - it's scheduled to finish in 3:52:48

 

[blade47]

Mine are real slow.

5.5-6 hours

P3-500e @ 620mhz (124mhz fsb)
Cas3 ram
Abit BX6rev2.0
client v2.4

If I up the fsb to 138mhz and use v2.70 I get just above 4 hours.
Too bad the 138mhz fsb was on borrowed ram.

 

[Assimilator1]

Silverback

That P3 @ 803 should be faster than that.You might find that SETI (at least) would run faster if you dropped the FSB down so you were able to run the RAM at CAS2 ,also if it's a VIA chipset board there are a load of tweaks you can do ,some of which make a big difference to SETI performance

 

[SilverBack]

What versions of Seti are you guys running?
2.73 here on all the machines.

 

[TuffGuy]

v2.76. 30mim slower than v2.70, but it does more calculations.

 

[cory]

well i run p3's at 150 mhz bus with cas 2 ram
(pretty picky about memory when running 150 mhz and cas 2.)

cas 3 vs cas 2 is like a 20% boost in bus mhz speed
so if i cant get a proc to run at 150 cas 2 i would rather run
at 143 cas 2 then 150 cas 3.

i tried the tiny bga 133mhz cas 2 and the
crucial 133mhz cas 2 ram and i can
push the curcial ram up to 150 mhz without
to much trouble but i could not push the tiny bga
as high.

i have not run anthing higher than the 2.04 client
(and most of my w/u's come from a linux cluster)

 

[Hellburner]

My P3 650@866 CL3 Cas 2-2-2 on a BH6 (BX chipset) with the 2.76 client looks like it's knocking them out between 3:15 - 5:00 hrs/wu.

 

[networkman]

Actually, I don't have any machines near that 5 hr/WU production currently.. my best are around 7hrs per WU. But I make up for this with 14 machines in my house.. six of which are dual-processor rigs.

 

[Stallion]

My 700@933 with mushkin PC133 rev1.5 hovers right around 5:20-5:50 but will drop below 5 hours if no gaussein(sp) is found.

I run text only ver 2.4

 

[Robor]

18 machines at work (worst is P233 & best is P3-550). Times range from 5hrs --> 23hrs depending on the WU.

4 machines at home (worst is C366@500 & best is P3-700@933 CAS 222). Times range from 3hrs --> 10hrs depending on the WU.

My best box: Abit BE6-2, P3-700@933, 256MB CAS 2-2-2 averages 3:15-4:00 per WU with 2.70 client.

Rob

 

[Stallion]

Ok, so just what do you have to do to get this 2.7 working. If you just load it will it over write 2.4 or do you need to delete 2.4? What's the secret?

 

[Zipperhead]

where can i get v.2.70?

Zip

 

[blade47]

v2.70 is a beta gui. It's an old beta the newest is v2.76 which is slower but does more science. Actually no one should still be running v2.70. The whole point in a beta is to find bugs. Since v2.76 is out if someone were to run a beta they should be running it to help find any problems. If you want v2.70 I'm sure someone will still give it to you.

 

[Zipperhead]

YES,i would like v.2.70 can someone please help.


Zip

 

[Mika]

I'm getting about 2.5hr per CPU on 2 dual Xeon 700's.

However, they will only be running Seti until they go into production (sometime this week probably)

Is it worth my upgrading to v2.7 over v2.4?

Mika

 

[TuffGuy]

Mika - oh yeah...

 

[Assimilator1]

Zipperhead

Checkout your 'I've joined thread'

SilverBack

I use CLi v2.4

 

[BadThad]

I can't seem to get under 5 hours on my fastest machine. It's a 700E@868, 512MB RAM @ 2-2-2 running the WinNT 2.4 text client. I'm not monitoring the times exactly, but it looks to be around 5.5 hours/wu.