Hi,
Is it possible that the work fetch request system can be subtly changed?
At
the moment, the user set's a cache by days in the client or the project
web site, this cache is then converted into seconds and the work fetch
logic will try to fill this cache.
For computers that are on and
crunching 24/7 this logic is fine, but for computers that only crunch
for a % of the day then this leads to them overfilling their cache and
possibly having work units time out or go to High Priority mode as they
will not finish in time.
For example, I currently have a cache
set to 4.5 days but only crunch for about 8 hours per day. The work
fetch request logic is currently asking for 0.86 + 388800.00 seconds of
work so potentially giving me 108 hours of work. Given the fact that in
reality I will only crunch for 36 hours (129600 seconds) of that 108
hours this is a massive overfill of the cache.
>From the project
websites we already track various statistics about how Boinc runs and is
connected to the network etc, could we not utilise these figures to be
able to give a realistic figure on that hosts up time and then use that
figure in the work fetch request logic?
Ghost
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
