Slow Times

[DaHazeMan]

I saw a thread (didn't read much - no time) about work time. When I restarted the seti client (had 25 units completed with an old 300MHz machine a long time ago) my average work unit time was slow. Someone mentioned that it would work itself out in the long run.

Well I'm up to 190 units now, and it's still averaging 27½ hours per work unit. So what's up? I'm running a 1.4GHz Athlon with 512MB SDRAM, WinXP Prof and I have a lot of up-time where I'm either sleeping, not here, or working (so nothing else bothering it). I have it running in the background and as the screensaver as well. I don't use Norton (NEVER) or have any other type of real-time virus scanner interrupting it. So why is it so slow? Any ideas? :confused:

[RampageIII]

You'll do much better running the commandline client with Setihide.

Download the command-line version (http://setiathome.ssl.berkeley.edu/unix.html) and put it in the same folder as Seti@home.

Download SetiHide (http://www.scheit.de/seti/setihide.html) and put that in the seti@home folder.

Wait for the current work unit to finish, close seti@home, remove the startup command, remove the screensaver.

Start SetiHide and it will take over the operation. Go through the settings and add caches and your good to go.

You should probably be crunching one every 5 hours or so.

[DaHazeMan]

Kewl :D

[DaHazeMan]

Oops...refreshed the browser in the morning and it must have reposted!

[DaHazeMan]

Well...in four days I've done 9 more work units and my average has already dropped by an hour per unit! Thanks for the tip RampageIII.

[RampageIII]

:cool: You're doing great! Glad to help. ;)