caching question now that may have to do this

[Burning Phoenix]

Seeing the trouble we are having today with seti server i was wondering exactly how this caching works. Not the settings but if i set my cache to 10 how does seti go about using these. I mean say the 1st unit is finished and i have setidriver set to auto transmit does it send this WU and proceed to work on wu 2 or does it go back and do the new #1 spot again?

[Morpheus]

SETI Driver processes the OLDEST cached WU first... (it manages it's own job que based on WU download date)

[JigPu]

If it works like I think it works (not a SETI Driver man myself... SETI Monitor...), when it finishes a WU, it stops SETI, and starts up a SETI in a diffrent folder. Driver DOES use diffrent folders all with SETI in them right??

If not, it just closes SETI, takes the result file when done, moves it to a diffrent directory, and moves a cached WU into the SETI directory. Then it restarts SETI.

JigPu

[Cy]

SETIQueue appears to work by acting as a proxy between each seti client and Berkeley. When one of them finishes a W/U it is pointing to the proxy. It gets a new W/U from the proxy and the proxy uploads completed W/Us every so often throughout the day. Works very well. It also provides some nice stats on each machines performance.

Cy

[lonewolf1983]

setidriver uses seperate folders to house the WU information
when crunching WU #1,it looks to folder #1 and crunches this until completion.
It then closes that down and starts on WU #2 in folder #2
it also transmits the completed WU and fills it with a new one
:)

[Morpheus]

Driver only maintains one copy of the client... as soon as one WU finishes, the next starts... THEN it looks to upload/download...

no crunching time lost...

[Wookie8662]

Originally posted by lonewolf1983
setidriver uses seperate folders to house the WU information
when crunching WU #1,it looks to folder #1 and crunches this until completion.
It then closes that down and starts on WU #2 in folder #2
it also transmits the completed WU and fills it with a new one
:)

Hmm, I have 18 WU's cached on one machine. When it did connect, it sent the WU's in folders #10 and #15.
Maybe going by WU dates, or the WU's that have been on the machine the longest?

[Mictlan]

WHen you install a fresh copy of SETIDriver it creates as many folders as cached unit has been set. The is complete *.sah files in each folder (lock, outfile, pid, results_header, state, user_info, version and work_unit). I really don't know where but in of those *.sah files but in one of them (I believe it must be some where in work_unit.sah) is the information on when you received the WU. When SETIDriver finishes one WU, it checks wich of all the remaining WU is the oldest and changes folder to crunch that one. If two WU were downloaded at about the same time then the smallest number of folder will be crunched.

I believe this information is stored in work_unit.sah as one day I moved a workunit fron one folder to the other and SETIDriver just ignored the new unit I placed in the original folder and moved to the WU I moved.

SETIDriver uses the command stop when finishing a WU, so when transmiting you are really running two instances of SETI clc. The transmit secuence is always donw in order, starting from the highest folder number and continuing in decreasing order until all WU has been sent.

All this information was obtained using SETIWatch, another monitoring program available here (http://members.shaw.ca/mloukko/SETI.html).

DISCLAMER: No animals were harmed during this investigation.

[Basher]

Ok here is a nice program made by Proze, It lets you see what the ar's are of cached WU's.