Re: BOINC has anything changed?

On Sat, 10 Jul 2004 23:40:48 +0100, "Skippy" <skippy�
@50leaguetitles.com> wrote:

Alan Woodford wrote:

That is the setting you need to change. Boinc doesn't download new
units until the expected run-time for the units you have is less than
the minimum time you have set. To keep a 1-day queue, you need to set
that to 1 to 1.5 days, then it will try and download when you have
less than 24 hours of work in your queue.

Use no more than 1 GB.

Leave at least 0.01 GB.

Use no more than 50% of total space.

Thanks, all help is appreciated.


You are welcome!

Alan Woodford




July 9, 2004
The core client now does preemptive scheduling of results. It time-slices
between results, maintaining the approximate project resource shares. The
work-fetch policy has also been modified; a single 'connection frequency'
parameter replaces the min/max buffer parameter, and the policy matches the
requirements of the CPU-scheduling policy.

http://boinc.berkeley.edu/


Looks like this setting has been replaced with a connection frequecy
parameter. I have my cache set at min 1 day max 2 days but I can never
download more than 1 WU at a time and as the WU only takes at the very max
4hrs to process on my machine so either the buffer settings don't work for
everybody or they expect you have your computer connected to the Net
permantly so the client can download WU's when it needs them rather than
storing them on the HD

Skip

Try moving the max out to say 4 days or even 7 days and see if you
don't get more units. If that doesn't work move the min out to 4 days
and the max to 7 days. Berkeley could also be restricting the total
number of units any one computer can download because of the recent
problems. Seems a bit restrictive in your case.