Quick question about SETI Driver....

[jar5tyle]

Hi, I'm getting more and more into SETI@home for Team Anandtech, I just got rid of the GUI version and got Seti driver for my comp and my dads. It's working great, much faster.

Anyway, my cache size for Seti Driver is 30 and I'm just making sure and want someone to clarify that after I have processed a WU, does seti driver automatically send in just that 1 WU and download another one to fill its place in the cache? I was under the impression that I was to process all 30 in the cache then send them all in, and receive 30 more. But that isn't the case, right? I just want to know and make sure where my WU's go, they are so precious! 😛

Oh and I have auto transmit enabled, and display transmit disabled, in case that's a factor.

Any help/reply would be appreciated, thanks.

 

[minendo]

You can set it to automatically transmit upon completion or manual transmit. The option is in teh upper right corner and is labeled "Auto Transmit."

 

[jar5tyle]

Yes and it does this after every WU processed? I thought with a cache stash it would wait till they were all processed

 

[JWMiddleton]

jar5tyle, Nope, it maintains the cache at the level you input. In your case 30 WUs. The purpose is to keep a cache in case you are unable to connect to S@H for n number of days. In the past it has been down for almost 1 week, but has been much better lately. If you uncheck "Auto Transmit", then you can manually submit WUs if you prefer to control it.

 

[jar5tyle]

Ohhhh... ok

Thank you for clarifying that JW

Appreciate it

 

[Strawa]

I think best way is to check: Display transmit and uncheck Auto transmit so CLI will finish all 30 wu and then u can manually transmit it and download new wus (i like to have it under my own control)

 

[RaySun2Be]

Originally posted by: Strawa
I think best way is to check: Display transmit and uncheck Auto transmit so CLI will finish all 30 wu and then u can manually transmit it and download new wus (i like to have it under my own control)

That works, except for us forgetful folk who would end up forgetting to check it, and forget to flush, then it would just sit there. Better for me to just let it submit automatically, that way I don't have to worry about it. 😀

That's what's nice about it, either way works, so you can setup to best suit your needs! 😀

 

[Strawa]

That works, except for us forgetful folk who would end up forgetting to check it, and forget to flush, then it would just sit there. Better for me to just let it submit automatically, that way I don't have to worry about it. 😀

That's what's nice about it, either way works, so you can setup to best suit your needs! 😀

yep, its good for nonstop connections, but then i cant see purpose of so big cache (30?), maybe it would be better to set it to 3 (just that cli have something to do between uploading result and downloadig new wu), ofcourse if he has nonstop connection 🙂

 

[Crazee]

Originally posted by: Strawa

yep, its good for nonstop connections, but then i cant see purpose of so big cache (30?), maybe it would be better to set it to 3 (just that cli have something to do between uploading result and downloadig new wu), ofcourse if he has nonstop connection 🙂

Thanks to the new pipe at Berkeley we haven't had too many problems lately, but just a few months ago you would know why people keep their cache settings high. I run a SetiQ at home (14 day supply) and I run SetiDriver on all my clients with at least a days supply of WUs. The reason I am paranoid is you never know when a nic card might fail, a port on a switch fails, etc. I like to have redundancy everywhere 😉