Am I doing it wrong?

{PMS}fishy · Jan 13, 2002

This is my first time using seti, but it seems like it is taking way to long for my computer to do 1 wu. It took almost 21 hours to do one, and you can see my computer in the sig. But friends have told me that there PIII 800s are doing 1 wu in 11 hours or so. Whats the deal. Im runing version 3.03 with the always on option.

TC · Jan 13, 2002

Dump the gui version and get the command line client. There's a difference of up to several hours regardless of how you configure the gui. Also keep in mind that using your computer for even simple tasks will increase completion times.

rogerdugans · Jan 13, 2002

If you are running the gui version it takes a lot longer to process a wu.

Try the command line client (clc) and it should speed up a lot.

I have a couple of old rigs (400/450 mhz) that are right around 18.5 hours, so you should definitely be able to do better!

Get more info HERE

*** thats what I get for being long winded: TC beat me to it! <LOL>***

Yodums · Jan 13, 2002

The PIII 800 should be doing WU's in 8 hours.

Setup a CLC and you'll be crunching 3x as faster as the slow GUI interface.

http://www.ocsetiteam.com/Instr1.htm

Theres the addy to setup the Command line Version.

Good Luck.
Happy Crunching.

XprincoX · Jan 13, 2002

will that client version work on XP too? its says it known to work on Windows 95, 98, 2000, NT but no XP? http://setiathome.ssl.berkeley.edu/unix.html

Yodums · Jan 13, 2002

Xprincox said:
will that client version work on XP too? its says it known to work on Windows 95, 98, 2000, NT but no XP? http://setiathome.ssl.berkeley.edu/unix.html

Use the link I gave you there's a zip for all files.

It works on all Windows and I'm on Windows XP and it works fine.

Yodums

LandShark · Jan 14, 2002

i've been run the CLC version + SETISpy + SETIDriver on my WinXP machine for 2 months already. didn't have any problem.

crunch on.........

XprincoX · Jan 14, 2002

hmmm... just switched to the clc version and have noticed that my system is reeeally laggy compared to the gui version. Should i just put the priority to low rather than normal?

LandShark · Jan 14, 2002

yup. if you DO use your computer.

i set all my rigs in "low" 'cos most of them are using everyday. and i did notice the lagging when i just set it to "only" normal. tried "high". man, makes me wait for anything forever!!!

Basher · Jan 14, 2002

Xprincox said:
hmmm... just switched to the clc version and have noticed that my system is reeeally laggy compared to the gui version. Should i just put the priority to low rather than normal?

Setting to anything other than low does not gain you anything. Low is the best setting else everything to slooooooooooooooow, setting it to high dows not really gain you any speed either.

TC · Jan 14, 2002

Use task manager to set the priority to "real time"

I actually tried that once and the system promptly froze - only time NTx has frozen on me

hallen · Jan 14, 2002

{PMS}fishy said:
It took almost 21 hours to do one

FAQ says changing screen density while SETI is running can slow it to a crawl. 256 color uses less resources.

http://setiathome.ssl.berkeley.edu/faq.html

lonewolf1983 · Jan 14, 2002

that screen res tweak is only to do with the GUI version
nothing to do with the CLC

hallen · Jan 14, 2002

TC said:
Dump the gui version and get the command line client.

By command line you mean: setiathome-3.03.i386-winnt-cmdline?

When I execute I get:

------------------------- clip -------------------------------
options:
-version show version info
-login log in
-countries show list of country codes
-proxy hostname

ort connect to SH server through specified
proxy server
-stop_after_process stop after current WU - do NOT send result
-stop_after_xfer stop after current WU - DO send result
-verbose print running status
-nolock skip multiple-instance check
-socks_server hostname

ort SOCKS proxy
-socks_user name SOCKS user name
-socks_passwd passwd SOCKS password
-cpu N set client to run on CPU N
------------------------- clip -------------------------------

Can you point me to some instructions and examples on how to use this to replace the GUI driver?

Thanks

Harvey

Basher · Jan 14, 2002

CLC install

hallen · Jan 14, 2002

Thank you Basher. I done that and it was helpful getting me started.
When I'm running it's with:

SETI Driver
SETI Spy

and when transmitting/receiving

setiathome-3.03.i386-winnt-cmdline kicks in.

I thought references to a non-GUI environment would mean eliminating SETI Driver and SETI Spy, which are GUI to me. and doing everything using

setiathome-3.03.i386-winnt-cmdline

which I can't find instructions on how to do anywhere.

deez · Jan 14, 2002

hallen...you are running command line with driver and spy...the GUI they are talking about is the screensaver mode which tends to increase times 33-50% over command line

driver and spy do not slow down the client

rogerdugans · Jan 14, 2002

deez said:
driver and spy do not slow down the client

Much. Maybe like a wu a year or something!

hallen · Jan 14, 2002

deez- Got it. Thanks. I'd love to do it in DOS with 32mb extended memory. With the big caches starting to appear I'd like to see the stats on keeping it all in L1 and L2 cache.

HP has a new 3mb L1 32mb L2 cache system:

http://www.lostcircuits.com/cpu/hp_pa8800/

Maybe that's what benz4140 is using

Am I doing it wrong?

{PMS}fishy

Senior Member

TC

Senior Seti Addict

rogerdugans

Linux challenged Senior, not that it stops me...

Yodums

Senior Member

XprincoX

bargain hunter

Yodums

Senior Member

LandShark

Super Shark Moderator

XprincoX

bargain hunter

LandShark

Super Shark Moderator

Basher

Senior Member

TC

Senior Seti Addict

hallen

Member

lonewolf1983

Member

hallen

Member

Basher

Senior Member

hallen

Member

deez

Member

rogerdugans

Linux challenged Senior, not that it stops me...

hallen

Member

Similar threads