Team Starfire World BOINC Forums @TSWB.org

Forum Home

Aggregated

Project Forums

Seti@Home

WU Caching...

WU Caching

5/2/2007 8:55:52 PM

TxRoadDawg

2 posts

WU Caching
(United States)

ok im dazed and confused and long for the good old days when i could just ask for 50 wu and seti dropped them on my machine. so what gives, who i gotta bribe out at berkeley to get more than 2 wus work at a time on my rigs here? Nothing really seems to make much sense on preferences, all im getting is one to work on and the next one to do.

On the other hand maybe this is a plot by a certain unmentioned canadian to forestall the inevitable pass that was only days away from happening..... /tiphat King

5/2/2007 9:17:41 PM

Kinguni

2157 posts

Re: WU Caching
(Canada)

Can't say I wasn't watching you're approach. Now we're both stalled in SETI since I keep a small cache and run backup projects (Rosetta and World Community Grid).

Cache is set on your General Preferences page. It can be done from any BOINC project you are attached to. The traditional BOINC way to set cache is be adjusting "Connect to network about every" from the default of .1 days to as high as 10, though it's recommended not to go higher than 7. I haven't played with the "Cache enough work for an additional" setting yet to know how well it works, but I believe that SETI@Home is the only project providing that setting.

For now (since no work is being generated for a few days) why not attach to Rosetta@home, just set the share lower (as low as 1) and then when Berkeley is sending WU's again you'll load right up if you adjust your cache settings.

5/3/2007 4:07:02 AM

Keck_Komputers

176 posts

Re: WU Caching
(United States)

The "Connect setting" should not be more than 1.4 if you are running SETI, because they have deadlines as short as 4 days. There is a nice chart of deadlines and maximum queue settings in the wiki. If you exceed the guidlines in the chart you may actually get less work due to the way the client works to meet deadlines.

The additional cache setting only works with 5.9.x and higher clients. I have limited experience with it's implications as well. However I expect that to achieve the maximum amount of queued work you would take the minimum deadline and subtract the connection frequency given by the chart to get the max value for this setting. In SETI that would be 4 - 1.4 = 2.6.

In all cases if you are attached to multiple projects you should base your calculations on the project with the shortest deadlines. If you are using a 5.4.x or earlier version of the client you also need to divide by the number of projects attached. (I highly recommend running at least version 5.8.11 of the core client, there are major improvements in that version.)

BOINCing since 2002/12/8

5/3/2007 11:17:20 AM