I've been doing some experimentation with running SETI GUI 3.03 in blank-screen saver mode, with OGR running at the same time.
The problem that I had running SETI before has returned. On occasion, I get a 'can't connect to server' problem, so it just keeps munching OGR until I maximize the SETI window. It will then connect with the SETI server and flush. This is the identical trouble that I had earlier this year running GUI ver. 2.? without running Dnet simultaneously, so I can't blame Dnet's client.
Is it time to set up a SETIQue? Is someone running a SETI proxy server that I can try to connect to?
As far as my experiment, it seems like OGR is taking up too much CPU time, slowing the SETI WU time to about 14 hours on my Celeron 366@550. I was doing around 8 hours with the old client. OGR production is down about 75%, so this all makes sense with the ver 3.03 performance hit. I wish that I could do something with the priorities to put more emphasis on SETI.
viz
The problem that I had running SETI before has returned. On occasion, I get a 'can't connect to server' problem, so it just keeps munching OGR until I maximize the SETI window. It will then connect with the SETI server and flush. This is the identical trouble that I had earlier this year running GUI ver. 2.? without running Dnet simultaneously, so I can't blame Dnet's client.
Is it time to set up a SETIQue? Is someone running a SETI proxy server that I can try to connect to?
As far as my experiment, it seems like OGR is taking up too much CPU time, slowing the SETI WU time to about 14 hours on my Celeron 366@550. I was doing around 8 hours with the old client. OGR production is down about 75%, so this all makes sense with the ver 3.03 performance hit. I wish that I could do something with the priorities to put more emphasis on SETI.
viz