
RobOC said:Good call with the public proxies, hadn't thought of that as contingencyHopefully I'll soon manage my 90 odd per day. How are we looking with our current output?

Sammael said:Unfortunately it seems a lot of my machines were busy folding still after I installed S@H. Folding has been removed from the machines, so now all machines should be crunching. Only did this at about 9 this morning though!!
I'm looking at adding more instances of S@H on the machines that are multiCPU capable, like the P4's and the 3 XEON Dual CPU servers!![]()


BillytheImpaler said:Remember that SETi Classic does not use too many system resources. I've never seen any bogging ussues with S@H. It almost always uses fewer than 30 MB RAM. Compare that to a QMD for FAH where the unit uses 300 MB RAM.
Maybe I should have stopped the boinc client running completely before adding classic - but looking at the running processes, it seems classic has a slightly higher priority than boinc, since it's classic not boinc that is hogging the idle (but it's not) CPU time.