I'm about to finish my first SETI cruncing...Now what???

[hipro5]

I'm about to finish my first SETI cruncing(96%)...Now what???
What shall I do next?....How shall I get another WU or send it back?...Sorry for the quesions but I'm totally "new" with this stuff.....

[Lorixnt2]

If you finish while you are online the client will automatically upload the result and get a new work unit.
If you are not online when you done go online and run the client
again.

[hipro5]

Now I'm online...what shall I do???...Shall I push the "transmit" button of the SETI driver???...or what???........Thanks for the help....:)

[Lorixnt2]

aaah u r using setidriver not the client ...
ok push that button and u done. It will upload the result and dload a new WU. It is not compulsory of course
if u have more than one WU in your seti driver cache.
It becomes compulsory when your cache is empty.

[hipro5]

OK....Thank you for your help....:)
I think I just did it....I'm crunching another one now....Is it posible to crunch more than one at the same time????....

[Lorixnt2]

If you use setidriver the app will be automatically aware if you
are on a dual and will automatically launch a double seti instance.
In that case it is better to chek the "set processor affinity" case.
Running more than one WU in a single CPU rig has been a subject of debates. Usually I don't do it. imho it is quite useless
even if there are supporters for that.

[Greg M]

If you have broadband, just set SETIDriver to transmit automatically and set your queue for a weeks worth of WU's. I have found using processor affinity is more trouble than it's worth. Crunching more than one WU per CPU doesn't enhance performance, unless you are using a P4 Xeon that has HyperThreading capability.

[hipro5]

No, I just have 64K ISDN....:( ....So it's beter to crunch only one WU per time???....Should I check the box "SETI Client Priority" to High???...Is there any difference at all on cruncing a WU...???

[Lorixnt2]

Originally posted by hipro5
No, I just have 64K ISDN....:( ....So it's beter to crunch only one WU per time???....Should I check the box "SETI Client Priority" to High???...Is there any difference at all on cruncing a WU...???

well hipro I always leave the priority low. Setting it high can in some cases hang your computer. But it is my personal opinion.
Setting "affinity" if I've well understood should lock the first process on cpu 0 and the 2nd on cpu1. Months ago I
tryed it an found a gain of a couple of minutes on a BP6 i don't use anymore and 2 P3TDDE. Since then I've always used it
on the duallies without probs.

[Greg M]

We've found in some situations the affinity doesn't 'stick' causing problems after reboots where one CPU is attempting to crunch more than one WU. Even manually tweaking the .cfg file didn't help. We have found leaving it off works every time, and saw absolutely no difference in completion times on our multiple dual servers and few quad servers.

If you're using dialup, go ahead and get online and fill up a queue and upload/download in batches. That way, the SeTIDriver will have enough to crunch while you're offline.

[hipro5]

Thanks for the replies dudes...I'm now crunching my third WU....Wish me luck.....:beer:

[Mictlan]

The great advantage of using SETIDriver is it's caching abilities. WIth those you don't need to be online always to get new WU, just connect sometime upload results, download new WU. This works quite good with dial-up connections.

As for crunching two instance of seti clc in only one CPU, as oyu dived the cycles between two WU your completiiton times will go up. There's been a deabte that when you add the time of crunching two WU one after another, is higger than the time it takes to crunch two WU at the same time, but in my personal experience that doesn't happen, so if you feel like it, try it and settle to your personal choice.

The affinity: Really there is almost no difference between normal and low, but setting it to high will devote all the CPU cycles to crunching and will cause slugginess in your keyborad and mouse, so it's more trouble than what you gain, as in normal or low yopu usually have 98% of the cycles grabbed by SETI and just 2% to explorer (including keyborad and mouse).

[ThePerfectCore]

SETIDriver got a bad mark from me when it crashed my 98SE machine that had racked up 17 days of uptime. I busted that CD-R on the spot.

I use SetiStash, which I find much more simple for what I do. I like to be able to check in on the CLI window every once in while, and SETIDriver wouldn't let me do that. And if even the slightest thing wasn't right, the icon would turn some annoying color, and stay that way until I fixed it.

SetiStash only yells when there's nothing left to be crunched, and automatically transmits WUs, no muss, no fuss. I run it on all machines in the farm.

[Codeman05]

About the whole "normal" vs "high" priority in Seti Driver.
On my main comp here, if I put it in high, I can't do anything else...now on my second rig I'm about to put online, since all its going to do is crunch, should I put it on high?? When "High" makes the OS "laggy", is it also hurting Seti's performance?
Thanks!
Codeman05

[Mictlan]

When you feel the rig "laggy" when setting the high priority, it exactly that SETI is grabing those few resurces it needs to get the inputting devices to work.....Even in dedicated crunchers, IMHO you only need to set the priority to normal, that way if you need to check a cruncher you can navigate around and do you stuff easily.

[Codeman05]

Makes sense, thx

[JigPu]

Of course, the actual time diffrences are very slight between normal and high (and realtime) priority. At low, I normaly get 85-99% of the CPU dedicated to SETI depending on what I'm doing. Normal brings it to 95-99%. High priority would probably only go 98-99%, and IMO wouldn't be worth it unless you honestly didn't care about checking the system more than once a month or something.

JigPu