running Seti on dual-cpu NT4 system

[Ben98SentraSE]

If I just run two instances will it just automatically run each on a different CPU? Is it that simple? I believe it is, just wanted to check.

(Assimilator1 starts sweating... )

 

[Hellburner]

NT handles splitting the workload just fine, I did some benchmarks ages ago letting NT do the process assignment and manually forcing affinities, there was no difference in completion times.

 

[networkman]

Use the CMD-LINE version; make two dirs and put the executable in each dir, like seti1 and seti2. Then make a batch file for each file with the parameters like this:

\seti1\setiathome.exe -verbose -cpu 1

\seti2\setiathome.exe -verbose -cpu 2

The "verbose" will enable some screen output so that you can see that the client is actually doing something.

Personally, I recommend using a program like SetiSpy(with a copy in each dir) to track the progress of each client.

 

[TuffGuy]

how much does the "-verbose" command affect times?

 

[networkman]

Not too much.. I think when I looked at this previously, there might have been a difference of ten minutes per work unit.. not enough in my opinion to keep me from using the -verbose switch.

 

[TuffGuy]

thanks.

 

[JHutch]

Also, you should definitely make sure you're running the 3.0 client. It is MUCH more dual CPU friendly (eats less bus bandwidth, so each CPU can actually get enough work to keep busy).

JHutch

 

[Assimilator1]

Duallies!??:Q *gulp* ,is it hot in here?...........

 

[Assimilator1]

Damn double post :| ,stupid slow dialup connection(today) :|

 

[blade47]

I've been wanting to build a dually rig myself. However I don't want to shell out the $$$$ for win2000 nor do I want to make my head spin by trying Linux. One of these days I'll take the plunge though.