How big is the maximun cache of WUs?


log in

Advanced search

Questions and Answers : Preferences : How big is the maximun cache of WUs?

Author Message
Profile [seti.international] Philip J. Fry
Volunteer tester
Avatar
Send message
Joined: 6 Apr 07
Posts: 6570
Credit: 50,810,778
RAC: 20,509
Germany
Message 796275 - Posted: 11 Aug 2008, 12:09:03 UTC


Your account/Computing preferences/

Computer is connected to the Internet about every x days

and

Maintain enough work for an additional y days


What is the max. I can insert for the x and y?

Is there a difference between the x and y?

For example if I insert x = 10 and y = 0 then I don't get WUs which are shorter than 10 days (deadline)?

____________


>Das Deutsche Cafe. The German Cafe.<

Profile Ageless
Avatar
Send message
Joined: 9 Jun 99
Posts: 11640
Credit: 2,008,452
RAC: 4,037
Netherlands
Message 796331 - Posted: 11 Aug 2008, 15:48:43 UTC

Connect about every x days, sets the frequency that BOINC contacts the project server to upload work, download new work and report work. It is not to be used as a method to queue up more work. For that you can use the Additional work buffer. Default at 1 day, if set to zero days it'll tell BOINC that you're on an always on connection.

Additional work buffer x days (max. 10), sets the amount of work that BOINC can ask buffer additionally per project. Default at 1 day, but can be set to zero as well. When set to zero, BOINC will ask for 1 second of work, translating into one task per project.

____________
Jord

- BOINC FAQ Service
- BOINC User Wiki


Real is just a matter of perception.

Aurora Borealis
Volunteer tester
Avatar
Send message
Joined: 14 Jan 01
Posts: 2975
Credit: 4,244,096
RAC: 2,870
Canada
Message 796357 - Posted: 11 Aug 2008, 16:56:21 UTC - in response to Message 796275.
Last modified: 11 Aug 2008, 17:00:33 UTC


For example if I insert x = 10 and y = 0 then I don't get WUs which are shorter than 10 days (deadline)?

The server will not send out WUs with deadlines shorter than your connect time you select to prevent missing deadlines. This is the reason the additional cache option was incorporated for people who wanted to maintain a larger cache. The Boinc manager also knows what you already have on hand and wont ask for additional work if the cached WU might not make deadline.

The primary goal of the system is to never miss a deadline, while still providing the user as much flexibility as possible.
____________
Questions? Answers are in the "Unofficial" BOINC Wiki.

Boinc V7.0.27
Win7 i5 3.33G 4GB, GTX470

John McLeod VII
Volunteer developer
Volunteer tester
Avatar
Send message
Joined: 15 Jul 99
Posts: 22343
Credit: 439,209
RAC: 396
United States
Message 799078 - Posted: 16 Aug 2008, 23:13:23 UTC - in response to Message 796357.


For example if I insert x = 10 and y = 0 then I don't get WUs which are shorter than 10 days (deadline)?

The server will not send out WUs with deadlines shorter than your connect time you select to prevent missing deadlines. This is the reason the additional cache option was incorporated for people who wanted to maintain a larger cache. The Boinc manager also knows what you already have on hand and wont ask for additional work if the cached WU might not make deadline.

The primary goal of the system is to never miss a deadline, while still providing the user as much flexibility as possible.

Is that actually implemented? Last I heard, it was merely proposed. Unless the server code is changed, you can get tasks that have deadlines shorter than your connect every X setting.
____________


BOINC WIKI

John McLeod VII
Volunteer developer
Volunteer tester
Avatar
Send message
Joined: 15 Jul 99
Posts: 22343
Credit: 439,209
RAC: 396
United States
Message 799079 - Posted: 16 Aug 2008, 23:16:00 UTC - in response to Message 796331.

Connect about every x days, sets the frequency that BOINC contacts the project server to upload work, download new work and report work. It is not to be used as a method to queue up more work. For that you can use the Additional work buffer. Default at 1 day, if set to zero days it'll tell BOINC that you're on an always on connection.

Additional work buffer x days (max. 10), sets the amount of work that BOINC can ask buffer additionally per project. Default at 1 day, but can be set to zero as well. When set to zero, BOINC will ask for 1 second of work, translating into one task per project.

Connect every X is a promise by the user that (s)he will allow BOINC to connect to the project server(s) at least that frequently. BOINC uses this for CPU scheduling and work fetch. Work must be finished and reported before the last connection BEFORE the deadline. BOINC assumes that the last connection prior will happen at Connect Every X before the report deadline, and therefore attempts to complete work at least this far in advance of the deadline.

Extra work is merely used for work fetch, but not for CPU scheduling.
____________


BOINC WIKI

Questions and Answers : Preferences : How big is the maximun cache of WUs?

Copyright © 2013 University of California