Seti@Home: More than 1 process??

[GroundedSailor]

Questions about SETI Driver:

What happens if you choose more than 1 in the Maximum Processes box? Does that work on more than 1 WU at a time?

If so, can I have say, 2 processes running through the night when the computer is not in use and shut down one in the daytime when I need the computer? Will shutting down 1 process cause loss of data?

I'm trying to see if I can increase my output while the two computers I use are idle. Speed TeAmAnandtech Along!!

Any help appreciated.

Thanks

 

[conjur]

Well, SetiDriver and the CLI use idle cycles if left in the Low priority mode so running two at once won't buy you anything.

 

[GroundedSailor]

I normally leave Seti in the High priority mode when I'm not using the computers. Would I still not gain anything?

Thanks

 

[Poof]

You can run multiple processes simultaneously on a single CPU but it won't really gain you anything (been there done that)...

The benefit is that if one process dies for some reason, at least your CPU won't go idle 'cause it'll be running the other process.

I routinely run multiple projects on a single CPU (eg., SETI + G@H, etc.).

 

[GroundedSailor]

Thanks. I'll just run 1 process on high priority and get what I can.

 

[Fingers]

you can run the united devices client if you want to run multiple things. seti takes priority over it, and considering the way points are awarded for ud, you can be helping both teams out greatly.

 

[GroundedSailor]

I was trying to see if I could increase the number of Seti WU's computed hence my questions. Shall look into UD.

Thanks

 

[Poof]

I was trying to see if I could increase the number of Seti WU's computed hence my questions.

In that case, if you think about what is happening, each new process of anything will take CPU time. You only have 100% to work with, so if 1 SETI process takes say 99% of that, the 2nd one (if run at the same priority) would also try to take 99%. But you obviously don't have ~200% available, so the 2 processes will split that 99%, each taking ~49%. Which means that each one is only running 1/2 as fast as before. Thus it will take twice as long to complete a single WU - although the actual reported CPU time will stay about the same. Ie., if it takes 5 hours/WU normally, it'll take ~10hrs before each process completes and is ready to upload! But... you'll end up with 2 results in those 10hrs (~the same as 1 result in 5hrs).

 

[conjur]

<< Thanks. I'll just run 1 process on high priority and get what I can. >>



High priority doesn't gain much either. I just leave all of mine on Low as then when it needs to upload/download WUs, that process isn't hindered.

 

[ober]

SETI Driver uses High priority for transmitting. I did this so that the Transmitting process will get the CPU time it needs to avoid dropping the IP connection if the user has other CPU intensive programs running at High Priority. The switch from "Idle" to "High" occurs 30 seconds after the transmitting process is created.

Mike.

 

[Civic2oo1x]

So running it in low as opposed to normal or high doesn't affect it at all right? I noticed that if I put it on normal or high, my system lags greatly.

 

[Confused]

Running Seti Driver with High or Normal priority will run the Seti CLI at normal or high priority, and therefore will fight for CPU usage with other applications, which is why the computer seems laggy.

Running it in Low should be fine no matter what you use the computer for, because if there are no other programs running, then Seti will get all the COU cycles anyway

As ober said, the transmitting/recieving of WUs is set to High priority so that it will take priority over other tasks, and will actually be done when it wants to be done!

Thanks ober for such a great program!

ConfusedBW

 

[GroundedSailor]

Thanks for a great program Ober and for everyone's input in this thread.