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

M

MikeyP

Member
Coming back from college for Christmas, I lost my RC5 herd for a few weeks. Being in the mood for something new, I've jumped on the Seti bandwagon. I did Seti a few months ago, but not recently. I made a new name MikeyP_TA, and joined the team🙂 Hearing that the CLI version is a bit faster, I downloaded it (v3.0.3). Yes, I know this version is slower, but it does more science🙂 I also set up SetiSpy and Seti Driver. The work unit I am currently working on is going to take about 20 hours, which seems very slow. I am getting 12.99CpF (cycles per flop) according to SetiSpy, whereas I should be getting below 6. Any suggestions?

<Edit> Thought you might like my specs🙂
Athlon Classic 700
128 MB PC133 (running @ 133 CAS2)
 
Welcome to the TeAm MikeyP! 🙂
Your estimated time does seem a little slow. However, I'm still using 3.0 so I don't have a feel for 3.3. I understand 3.3 may take upwards of 50% longer to complete. Also, you may be working one of the dreaded low angle range w/u's. Those things will add 30-50% to your time.
I'm don't own any AMD so I can't help much with specifics, but it looks as though there should not be a memory bandwidth problem w/cas2 @133.
You may want to just let it run a few w/u's and ck. the avg. before passing judgement on the system.
Have a great day!

Phiton
 
When I turn off Seti Driver, the performance increases dramatically. Is this normal? If not, any tips on how to set it up?
 
Mikeyp

Welcome back to the search🙂.
If you took the time taken from SETIspy at the very beggining of the WU then it is probably not accurate ,you'll get a better idea once you've done at least 50% of the WU ,but really you need to do Phiton says &amp; do some WU's before you know the WU times.Preferably at least 5.
BTW your 1 of our pioneers in the useage of V3.03 CLi 😉 ,we'd be very interested to see what WU times you get.🙂.
Also ,aside from the CAS timing ,what are your other memory timings set to?

As for SETI driver it shouldn't use barely any cpu time ,anyone else?
 
Not at all normal. Seti Driver should be using less than .05% of your processing power. CTL-ALT-DEL and see what you have in the close programs box. There should be one instance of Seti@home-3, Seti Driver, and winoldap. You may want to use a task manager to help determine what is going on.
I'm using v1.6.2.0 w/cli 3.0, have not seen this problem. Have not heard of a compatability issue involving seti driver and v3.03. Let us know what you find with this.
 
Thanks Phiton, that did the trick! I was running two clients at the same time. One through SETISpy, and one through Driver. I didn't have them configured correctly. Now, I'm doing WU's in 8-8.5 hours, version 3.3, Athlon 700.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top