In article <v7sqgvs6q3hogdofrlb16f3rmktdel0o33@4ax.com>, f/f george
<an16365785@nonanon.penet.de> writes

If you also get a copy of Seti Watch it will show you the actual
processing times on each work unit per processor. I am not sure about
HT but it does work on my dual 300 compaq server.
Just remember to set the cache level at twice whatever the individual
machine does at the moment for dual and above processors. That way it
can handle units being returned at the same time.
Like my dual does 2 at a time so my cache level is 4. I use Seti Queue
on a different machine so I only need the minimum on each machine.

I agree this is the best way for multi-proc systems and networks.
Caching with SETI Que, dishing out to SETI Driver (local small cache)
and SETI Spy/SETI Watch monitoring.

Like you, I have a small home network. This currently consists of the
dual proc Xeon, a dual proc P3 and single proc P3. All run under Win2K
pro, and are peer-to-peer networked.

I am still playing with the Xeon system. When this is complete I want to
set it up as a SETI Que proxy, for the different SETI Drivers to send
completed units to and collect new WUs.

Have you any advice for when I move to this position, please?
-- 
John Clark