• 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.

Seti: Systems Running Slow?

M

moonshinemadness

Platinum Member
Hey guys i have 2 rigs running seti but im sure theyre not running at full speed as they should, what do you reckon?

Asus A7N8X Deluxe
XP 1600+(Palamino) @ Stock Speed...needs o/cing again
512 DDR 2700
XP Pro

This is usually churning WU's out at anything between 2:30 and 4 hours

My other Rig is

ESC K7S5A
1.3ghz T'Bird @ Stcock Speed
512 DDR 2700

Windows 98

I only just built this rig and the first WU it started is looking at 6hours 30 mins...I cant see how the difference can be so great. Any ideas? And ideas on how to speed up would be good to.

PS Im using the CLI client
 
Times sound about right to me.

However, get a TBred 1700+ from NewEgg ($42) and replace that 1600+. Then you have yourself a true overclocking project.😛
 
Could be that 1st WU was a VLAR. I've had those take over 5 hours on my XP1800 running Win 98SE(averages 3.5 hours). Wait & see what the actual CPU time is when it's done.



2.5 hour WU's on that XP1600 @ stock speed? WOW!
I've yet to hit the sub 3 hour WU on the fastest of my 2 systems.
Name: Polaris
CPU: AMD XP 1800 @ stock speed
MB: Abit KX7
RAM: 512mb Corsair PC2700
OS: Windows XP Home
Fastest time- 3:01:03 (6.656 AR)
 
Spacehead seems to be on the right track. That time for the 1.3 seems a little high, but that may be due to the AR. Your times should be around 5:30 in my opinion.

Seti Timer Check this out. my java is acting up, but it ought to tell you what you want.
 
Originally posted by: Spacehead
Could be that 1st WU was a VLAR. I've had those take over 5 hours on my XP1800 running Win 98SE(averages 3.5 hours). Wait & see what the actual CPU time is when it's done.



2.5 hour WU's on that XP1600 @ stock speed? WOW!
I've yet to hit the sub 3 hour WU on the fastest of my 2 systems.
Name: Polaris
CPU: AMD XP 1800 @ stock speed
MB: Abit KX7
RAM: 512mb Corsair PC2700
OS: Windows XP Home
Fastest time- 3:01:03 (6.656 AR)
Click to expand...

I think your right its doing its second WU now and its looking at 1hour 53 mins not to shabby 😀

 
Tbirds are much slower than XP`s in seti. A 1gig duron is probably faster than a 1.3 tbird at seti. I think the SSE instuction set with the palimino core is what makes makes the difference.
 
I dunno about Durons being fast at SETI... for the short while I used it, it took me about 15 hours (or it may have been more, I can't remember) to get to 33% of a WU with a Duron 900 🙁

Now that I think about it, that's WAY too high compared to the times you guys are getting. Has the SETI client become, oh, I don't know, 600% faster in the last 6 months? 😛
 
A 900 duron would be a spitfire (tbird) core. A 1gig is a morgan (palimino) core. That is the big difference.
 
Allio3,
45 hours for 1 WU IS excessive. Are you running the screensaver or the CLI? Sounds like you might be running the screensaver version. If not running the screensaver, then it sounds like you have other programs running that are using system resources and not letting SETI get enough CPU time.

I was running a Duron 650@850mhz, and I my average times were around 8 hours using the CLI client running Win2KPro.
 
Most of that was with the screensaver, but I switched to the cli later when I realised my times were so bad. Didn't make a difference. Oddly enough, when I upgraded to a 1700+, the times also stayed the same. Maybe there was something a bit buggy with my work unit, I don't know 🙁
 
Could have been a VLAR, they can take awhile. I would also look at other programs, hidden services chewing up system resources. The CLI is much faster than the screensaver, and those times are way off with a 1700+. I would recommend letting it run several different WUs to see the times, or download the benchmark .417 angle range WU from Ars Technica and run that one.

Something wasn't right, that's for sure.
 
VLAR = Very Low Angle Range like a 0.05 angle range. Can't remember the scientific explanation, but usually, the higher the angle the faster the processing. 🙂
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top