Slow WU Completion

MrSanderzX

Member
Feb 14, 2002
111
0
0
Question, I have a 800Mhz PIII with 768 MB of RAM, I am aware that that much RAM makes no difference, and I also have 1.0Ghz Celeron with 1024 MB of RAM. The 800 is only pushing maybe 2 WUs a day while the 1.0 is pushing at best 1 WU a day. :( Any one have any thoughts on how to fix this or make it better. BTW each computer is hardly being used each day. Thanks.

MrSanderzX
 

conjur

No Lifer
Jun 7, 2001
58,686
3
0
The speed of the RAM matters a lot more than the amount of the RAM.

My server with a single PIII-933 does a WU in a little over 6 hrs and it's PC133 RAM running W2K.

What's your OS?

Also, if you're not going thru a SetiQueue, I think SetiSpy can tell the AR of the WU. If it's a small value, like 0.01 or something, that would increase the WU times.
 

MrSanderzX

Member
Feb 14, 2002
111
0
0
conjur

My RAM is PC133 and both are loaded with Win2k. I am using SetiQueue. If that helps at all. I am taking around 12 to 15 hours on the 800 and 23 hours on the 1.0.

MrSanderzX
 

networkman

Lifer
Apr 23, 2000
10,436
1
0
Are you using the CLI client or the pretty GUI client? That would make ALOT of difference as the GUI version can be quite a bit slower. Is there a screen saver running? The OpenGL screen savers can take quite a bit of CPU power away from the Seti client. If it's an option in your Bios, see if you can change the CAS latency from 3 to 2.

All of those may help your times; just so you know, I have a dual p3-733@787(143 fsb) and each cpu generally takes between 10 and 11 hours per WU. :( Oh well.. that's with Win2K also.
 

Polo

Diamond Member
Oct 10, 1999
4,185
0
0
If you are using the screen saver then swith to the CLI version with SETIDriver. That will cut your times by about 50%.
 

DeathLiRE

Member
Jan 15, 2002
63
0
0
You know your problem probably isn't any screensavers or anything...it's your "Celeron" celerons have lowerd L2 Cache
than your P3...depending on if you have a normal p3 or a p3-syou could have 512 L2 on that baby...
Remember, the more L2 cache you have the more power you have for seti....
my AMD sorry to say only has 256k L2.....but i'm running it at 1200@1600mhz it does about 5-6 a day...(when it keeps cooled good)
 

DeathLiRE

Member
Jan 15, 2002
63
0
0
oh man..i didn't notice that..where you said it takes about 23 hours.....
my old pentium1 mmx 266 could do one in 24 hours.....
you might need to reformat your computer or something...maybe overheating...you could have very many problems...but they are hard to tell..need some info
 

MrSanderzX

Member
Feb 14, 2002
111
0
0
My P-III is from Gateway just under two years ago. I have a fresh OS on both systems. It is really urking me. I am not using the Screen Saver or anything like that, all my programs are from the TeAm link, so I am using the CLI.

MrSanderzX
 

BigFatCow

Diamond Member
Aug 11, 2001
3,373
1
0
do ctrl alt del, and see what is taking up all of your CPU cycles, then find what that program is and do something to turn it off, or delete it.
 

Assimilator1

Elite Member
Nov 4, 1999
24,165
524
126
MrSanderzX
I had a PIII 650@820 on a BX chipset which did most WU's in 7hrs ,a PIII 733@814 I have has sofar done WU's in under 8hrs.

If you are running the text version of SETI(CLi) then you definalty have something stealing cpu power ,try Taskinfo to see if your are losing cpu power to anything
 

wirelessenabled

Platinum Member
Feb 5, 2001
2,192
44
91
Mt P-III 600E@800 @133 MHz FSB has averaged 7hr34m over the last couple hundred WUs with kids playing games etc.
 

Rattledagger

Elite Member
Feb 5, 2001
2,994
19
81
The 12-15 and 23 hours, is this average CPU-time as reported by SetiQueue, or average time?
If these 2 times is nearly identical, take a look on power-saving-settings in wink2 and in bios. You've probably got some setting for turning down the speed of the cpu then you haven't hit a key for x minutes... If you've set the hd to stop after x minutes, disable this.
Also check in bios to make sure the cpu-caches are enabled.

If it's the average time, and the CPU-time is much lower than 12-15 and 23 hours, check Task Manager, and disable the interfering program. Virus-scanners and netbrowsers is the most likely offenders.