I have my seti settings for 20 days of work, however it keeps only downloading 1 work unit at a time, and I can do one in 3 hrs.

Any suggestions on where to look for a change, or is it set this way for a reason.. Thanks

If you ever do get 20 days of work you won't be able to run them all anyway because there is a 14 day deadline on all work units that starts the day you download them...

Agreed

Ten Days is the maximum I would set.

Maybe that's why you are having problems download?
[url=http://acidtrax.net/forum/index.php]
<a>

Yes, I usually keep my Preferences for Seti @ 9-11 days, that way if it gives me a few extra I'll still be able to get them done before the Deadline...

Never thought of those-- I changed it to 10, then reset the project. Does it matter that I have it set so that s@H is running 80% and climateprediction is 20% ?

Probably, because BOINC will take into account how much CP work is on your system (several hundred hours, usually), and will only "top up" with smaller projects like SETI, Predictor, etc....

The point is for you to have enough work that if everything goes down for 10 days (or whatever) you won't run out.

At least that's the way I've been interpretting it...




Feel free to take a look inside my brain

Thats what I am trying to do, is to load in a bunch of WU's then disable network access. But with climate prediction running, I think that is what is causing it only to take 1 wu at a time, unless someone else can help me out on this one..

> Probably, because BOINC will take into account how much CP work is on your
> system (several hundred hours, usually), and will only "top up" with smaller
> projects like SETI, Predictor, etc....
>
> The point is for you to have enough work that if everything goes down for 10
> days (or whatever) you won't run out.
>
> At least that's the way I've been interpretting it...
>

>
>
> Feel free to take a look inside my
> brain
>

Just remember that a single CPDN wu will keep you busy for almost a month - which should be enough =)

Good point--- wanted more time to S@H over CPDN thats why I was trying to get more work for Seti, then work on CPDN when there was no work or during less time.

> Just remember that a single CPDN wu will keep you busy for almost a month -
> which should be enough =)
>

>>I have my seti settings for 20 days of work,

With all the work that's been lost here over the last few weeks I've cut my cache down to one or two units, and top up regularly. If it all goes pear-shaped again I may run out of work, but past experience suggests that any work I do during a major outage is wasted anyway.



Giskard - the first telepathic robot.

What is your "at least" days set to?

This should set the minimum # of WU's to download at one time as well as the trip point to "restock" your queue.

The "at most" setting is the maximum, not to exceed, limit.

thus "keep at least 10 but at most 13" days of work should keep your
queue pretty damn full.

There still remains the 50 WU download/day limit to any single client.

-P

> If you ever do get 20 days of work you won't be able to run them all anyway
> because there is a 14 day deadline on all work units that starts the day you
> download them...
>
>

Thats not completely true.
On my old crunching machine:
Before beginnig crunching a WU Boinc thinks it will need 7:20h. Effectivly it needs 5:10h for a WU. In addition some WUs only need 2 or 3 minutes. So it could possible WUs for 20 days crunch in 14 days.

> What is your "at least" days set to?
>
> This should set the minimum # of WU's to download at one time as well as the
> trip point to "restock" your queue.
>
> The "at most" setting is the maximum, not to exceed, limit.
>
> thus "keep at least 10 but at most 13" days of work should keep your
> queue pretty damn full.
>
> There still remains the 50 WU download/day limit to any single client.
>
> -P
>
The maximum setting tells the client when to stop downloading, but it will always be exceeded by part of a workunit. So if your maximum would cut off at 5.2 workunits you will download 6 workunits.

I have not quite figured out how this applies with the new preemptive scheduler yet. But I definately advise a low setting (1 to 2 days) until the bugs are worked out. The client may be downloading your specified amount of work for each project right now.

John Keck -- BOINCing since 2002/12/08 --

> > If you ever do get 20 days of work you won't be able to run them all
> anyway
> > because there is a 14 day deadline on all work units that starts the day
> you
> > download them...
> >
> >
>
> Thats not completely true.
> On my old crunching machine:
> Before beginnig crunching a WU Boinc thinks it will need 7:20h. Effectivly it
> needs 5:10h for a WU. In addition some WUs only need 2 or 3 minutes. So it
> could possible WUs for 20 days crunch in 14 days.
>
>

um seems to me u need to run benchmark then it should tweek the time boinc thinks it need to closer to when it really will take
<p align="center"> </p>

> um seems to me u need to run benchmark then it should tweek the time boinc
> thinks it need to closer to when it really will take
>
The benchmark is runnig so often and every time the result is the same with a deviation of +/- 5 minutes

> Never thought of those-- I changed it to 10, then reset the project. Does it
> matter that I have it set so that s@H is running 80% and climateprediction
> is 20% ?

Eek! You don't want to be resetting projects whenever you make a preference change. "Update" is what you should be doing.

> Probably, because BOINC will take into account how much CP work is on your
> system (several hundred hours, usually), and will only "top up" with smaller
> projects like SETI, Predictor, etc....

It doesn't quite work like that. You will still download a cache full of other projects WUs even if you have a CPDN WU sitting there.