• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Sluggish performence running seti@home 3.03 on athlon 600

T

toft-dk

Diamond Member
Just started running seti@home ver. 3.03 ( grafic ) on a athlon 600 ,128mb PC100 ram
MSI 6167 motherboard. WD 18 Gb @ 7200 rpm . leadtek winfast geforce 256 sdr.
After installing SETI Spy i have tried to compare with other configurations, and
they practically all run faster than mine.
An athlon should run at about 5,5 and mine runs at about 9 - 11.

That's bad

What can i do !!!!!


Newbee to seti@home
 
to increase speed set your screensaver to blank screen and should help things a little, also version 3.03 is much! slower than the other versions so make sure the time your comparing it to are from version 3.03
 
I'm already doing that !!!
I know my mobo sucks
I have no oc possibilities, so now i'm down to memory timings ??

 
The times actually sound pretty reasonable, on my Athlon 700, I have averaged 9:02:47 on 121 work units on 3.03.
 
Times fall right in line.........

But you may want to run the CLI to pick up the speed a bit. If you want to see what's going on run the Client in conjuction with SETISpy.

3.03 runs like a three legged dog and is actually driving many people to other DC's.

 
The 5.5 hour times you are looking at are for the version 3.0 client, which is no longer available (and results are no longer accepted). Your times look just about right for version 3.03 and as has been recommended, would problably drop just a bit with the command line client.
 
I may not have expressed myself right.
the 9 - 11 i score are not hours it's CpF
that makes it very slow !!!!
the completiontime for my first WU was about 51 hours.
the second on that mashine was approx. 17 hours.
It should be able to run much faster than that.




 
Make sure your screen saver is set to go blank after a minute or two. The pretty graphics drain tons of CPU power!
 
toft dk

Ref 'blank screen' ,we're not talking about the monitor shut down setting ,its the SETI screensaver setting we're referring to ,just incase theirs any confusion🙂

BTW I hope you join our team ,lots of helpful & friendly people here 🙂
 
it sounds like you're drawing the graphics, which take about 1/3 of cpu time. and you might have some other programs taking up time as well.
 
Sorry if I've added to the confussion........
Several points that may help.

1. If running the Screen saver version.....set up in the options to run all the time, and keep it minimized. Under your desktop settings select blank screen as your screen saver of choise.
There's really not that much difference between the CMD-Line and graphics version if run like that. However, if you run the screen saver as it was intended, (like a screen saver) OUCH!!!
You could easily double and even tripple your WU times.........

2. Assuming you've already done this and still have the occasional SSSSLLLLOOOOOOOOOW WU, you have probably run into what we refer to as VLAR (Very Low Angle Range)units. You can tell these by opening a WU file with a text editor and looking here:

type=work unit
task=seti
version=256
name=10no00aa.2359.29074.654818.168
end_header
data_type=encoded
data_class=0
splitter_version=0x0008
start_ra= 9.007
start_dec= 18.21
end_ra= 8.988
end_dec= 14.87
angle_range= 3.354
time_recorded= 2451859.88956 (Sat Nov 11 09:20:57 2000)

This is a quick WU.....notice the angle range.......

If the angle range drops down below 0.400......they get Slow, like this one:

type=work unit
task=seti
version=256
name=17dc00aa.20873.5648.865892.139
end_header
data_type=encoded
data_class=0
splitter_version=0x0008
start_ra=23.019
start_dec= 31.96
end_ra=23.017
end_dec= 31.94
angle_range= 0.025
time_recorded= 2451896.44465 (Sun Dec 17 22:40:17 2000)

For some reason the Cycles/Flop drop way down for these units. I run a WU in about 6 hours on my system at home......but I have taken up to 18 hours for a VLAR......

Some people are deleting them, others are saving them, in the belief that this bug will be worked out in the next Client release, and others ...like me....just run them like all the others and continue on.

I hope all this helps..............
 
Thank for the tips.

I changed from grafic to CMD-Line on my 600 athlon and the last WU i did
in 9, something hours The CpF was averaged on 5,09.

So as soon my other computer finishes the WU it's working on i will change
that to CMD-Line too. ( see if it helps there too )

There is no way to do it while in progress i gather ?

 
No it will just restart the WU.
BTW you'll want to do about 10 WU's before you know your average WU time

Gazoooo

That about covers it 🙂
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top