• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

How much does SetiSpy slow down the processing?

supernova87a

Senior member
How much does SetiSpy slow down the processing? I've got the command line version of s@h, so I can't really tell how long the work units are taking without having setispy on...
 
You can also use SETIWatch to check the client's progress. Just have it in the same folder as the CLI (command line client). There's a link to SETIWatch at the page the bottom link in my sig goes to.

Also, do you have the blank screen screensaver turned on? Most screensavers take a lot of CPU power so they can really hurt your SETI times.
 
supernova87a

Taskinfo tells me that SETIspy peaks at a maximium of 0.34% cpu useage.Thats on my Cel 366 @ 550.

The only exception is that I sometimes have a problem with SETIspy where it partially crashes (cant close the box pressing 'X')then it takes up 97% cpu time! :Q.It only does this when spying on the local client ,it has never done this on remote clients.

Anyone else had that problem?
 
I would expect your CPU temp to rise 3 deg when running seti, regardless of setispy, but setispy by itself should not cause a rise in temp (with or without seti client), if you follow!
 
You have to put SetiSpy in the directory with the client on the remote computer, then make a shortcut to the client's copy of SetiSpy on the computer you want to use for monitoring. The only problem with doing this is you have to have a separate copy of SetiSpy running for each computer you are monitoring, so if you have more than one or two you want to watch, SetiWatch is probably a better option..
 
Back
Top