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

Slow Seti@Home On Fast System

B

barlav

Senior member
I'm brand new with seti@home and I'm currently working on my first unit. I have a 1 Ghz AMD T-Bird with 256 MB ram and I'm only 38% into my first unit after about 10 hours. This seems really wrong to me. I've read somehwere that low angle units take long regardless of the system? So, what is considered a low angle unit. The one I'm currently running through is 0.079. Is this considered low? My system is 100% optimized so I'm assuming my speed problem is on the seti@home end. I have it running all the time. Also, most of the time it's the only thing running. Any help would be appreciated. Thanks! 🙂
 
Hey barlav, welcome to the TeAm!! 😎

Are you running the screensaver client? And if so are you letting it show the "pretty graphics"? Those graphics slow the WU times down bad 🙁 If you're using the graphics put it to blank screen in 1-5 mins in settings for the screensaver... also check that you don't have any other powersaving features enabled such as standby mode or turn off HDs 😉

Hope this helps some, good luck

With love and respect your fellow TA member

Two-Face
My stats:
RC5
OGR-25
Seti
Gamma Flux
 
barlav: Like TwoFace said, make sure you're not displaying the graphics if you're using the GUI version. It will kill your production time because it takes a lot of CPU power to display the graphics. Also, if you do run another screen saver make sure it's not CPU intensive. There are a lot of screen savers that will really make your production suffer. I prefer to use "flying through space" or "starfield simulation" depending on which operating systme you're using. Those screen savers are good because they don't hurt your production.

Glad to have you aboard!

Rob
 
Thanks guys. I will get rid of screen saver mode and just keep it running at all times. I am going to put my monitor in power saving mode instead of using a screen saver and see how that improves things.
 
barlav - there's also a text client that most people here run if you want faster times and don't necessarily need the graphics. You'll notice the difference if you opt to use that instead.
 
beinvenidos a TeAm anandtech!

<a target=new href="http://setiathome.ssl.berkeley.edu/unix.html
">command line clients</a>

theres the command line clients, you probably are running windows of some flavor so you should get i386-winnt-cmdline.exe. if you're running linux or something else, find your flavor of operating system after i386.
 
Hi barlav!

You asked:



<< I've read somehwere that low angle units take long regardless of the system? So, what is considered a low angle unit. The one I'm currently running through is 0.079 >>



Yes, they do take longer and you are crunching on one! 🙁 A VLAR WU is one that has an angle-range of less than .1
 
Thanks for all your replies. They are helping a lot. I will try one of the command line clients. Is there anything special I need to run it? Do I need to perform some sort of setup or put it in some sort of batch? Thanks! 🙂
 
all i do is double click the CLI. you can use setispy or setidriver to start it automagically. i use both. setidriver caches work units so you can ride out server downtime, setispy generates all sorts of little data about your work units.

oh, when you change over from GUI to CLI, wait until the GUI is done with the work unit you're on, if you're far into it, before closing it and starting the CLI. that way you don't lose work switching between clients.
 
Thanks ElFenix. I will wait for my current WU to finish before switching. Will the command line client work faster than the GUI even if I rarely view the GUI interface and not use it as a screen saver? I would think so but I just wanted to double check. Thanks.
 
yep, the command line is generally a few minutes faster even then. not sure why, i figure it would run the same routines. theres one exception: for the windows CLI client there is a bug with the very low angle range work units that makes them take longer than normal. poof is collecting information to try to figure out what causes the bug, seems to have something to do with OS patches.
 
3.03 does 50% more work than 3.0.

uh oh... not moving up the stats much anymore... stuck at 99.45... need more power! (slowing getting components for a really fast kt133a athlon 😉 )
 
Yes, the Seti Driver/CL Client combo works very nice. I seem to averaging around 4.5 hr/WU with those two programs. I also did the GUI client first and it is much slower...
 
I just installed the CL and the Seti Client and I can see a big difference in performance already. Thanks for all of you suggestions. I'm now going to download SetiSpy and play around with that too! 🙂
 
barlav

Most of the speed difference between the CLi &amp; GUI is usually because the GUI had the graphics showing.With the GUI set to 'blank screen' or run minimsed the difference between GUI &amp; CLI is small.But the CLI is still faster 🙂

Oh &amp; Welcome to the Team 😀
What's your SETI name BTW?
 
I'm now running the Command line version along with SetiDriver and SetiSpy and I'm averging 5-7 Hr's/ WU which is much better for my 1 Ghz system. Thanks again for all the help 🙂
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top