Changes between Version 4 and Version 5 of WorkDistribution

Timestamp:

Jun 30, 2008, 12:30:32 PM (16 years ago)

Author:

davea

Comment:

--

WorkDistribution

@@ -5 +5 @@
 <work_req_seconds>X</work_req_seconds>
 }}}
-element in a scheduler RPC request message. This asks the scheduler to return enough work to keep all the host's processors busy for X seconds, given the host's typical usage (i.e. the fraction of time it's turned off or BOINC is suspended, and the other processes that it executes).
+element in a scheduler RPC request message.
+This asks the scheduler to return enough work to keep all the host's processors busy for X seconds,
+given the host's typical usage (i.e. the fraction of time it's turned off or BOINC is suspended,
+and the other processes that it executes).
 
-BOINC's work distribution policy addresses the (sometimes conflicting) goals of keeping hosts as busy as possible, while minimizing the impact of 
+BOINC's work distribution policy addresses the (sometimes conflicting) goals of keeping hosts as busy as possible,
+while minimizing the impact of 
 
  * Hosts that repeatedly return results with error outcomes, due to a host-specific problem.
@@ -22 +26 @@
  * A result is not sent if [HomogeneousRedundancy homogeneous redundancy] is enabled and another result of the same workunit has been sent to a different type of host.
 
-???If there are several results satisfying the requirments above, which one will be chosen and sent to the host????
+In general, the BOINC scheduler responds to a work request by enumerating unsent results from the database,
+filtering them by the above criteria, sending them to the host,
+and continuing until requested duration X is reached.
 
-In general, the BOINC scheduler responds to a work request by enumerating unsent results from the database, filtering them by the above criteria, sending them to the host, and continuing until requested duration X is reached.
-
-For projects that have very large input files, each of which is used by many workunits, BOINC offers an alternative work distribution policy called [LocalityScheduling locality scheduling].
+For projects that have very large input files, each of which is used by many workunits,
+BOINC offers an alternative work distribution policy called [LocalityScheduling locality scheduling].