Changes between Version 96 and Version 97 of ProjectOptions

Timestamp:

Jun 1, 2010, 3:55:30 PM (14 years ago)

Author:

davea

Comment:

--

ProjectOptions

@@ -12 +12 @@
 }}}
 
-== Scheduler: general ==
-
+== Scheduler ==
+
+=== General ===
 {{{
 <one_result_per_user_per_wu/>
@@ -116 +117 @@
 If true, ignore duration correction factor.
 Use this temporarily if you've made a major change to your workunit FLOPS estimates.
-== Scheduler: job-cache scheduling ==
+=== Job-cache scheduling ===
 
 This is the default.
@@ -132 +133 @@
 The size of the feeder's enumeration query.  Default is 200.
 
-== Scheduler: matchmaker scheduling ==
+=== Matchmaker scheduling ===
 
 This is a variant of job-cache scheduling.
@@ -156 +157 @@
 to maintain statistics on the distribution of host speeds.
 
-== Scheduler: accelerating retries ==
+=== Accelerating retries ===
 
 The goal of this mechanism (which works with job-cache and matchmaker scheduling,
@@ -202 +203 @@
 To do so, set the workunit's priority to '''reliable_on_priority''' or greater.
 
-== Scheduler: locality scheduling ==
+=== Locality scheduling ===
 {{{
 <locality_scheduling/>
@@ -217 +218 @@
 This element only has an effect when used in conjunction with the previous locality scheduling element. It tells the scheduler to use 'trigger files' to inform the project that more work is needed for specific files. The period is the number of seconds which the scheduler will wait to see if the project can create additional work. Together with project-specific daemons or scripts this can be used for 'just-in-time' workunit creation. See [LocalityScheduling Locality Scheduling].
 
-== Scheduler: job retransmission ==
+=== Job retransmission ===
 {{{
 <resend_lost_results> 0|1 </resend_lost_results>
@@ -231 +232 @@
 
 
-== Scheduler: data distribution ==
+=== Data distribution ===
 {{{
 <replace_download_url_by_timezone>URL</replace_download_url_by_timezone>
@@ -242 +243 @@
 When creating work, keep a record (in files called foo.md5) of the file length and md5 sum of data files and executables. This can greatly reduce the time needed to create work, if (1) these files are re-used, and (2) there are many of these files, and (3) reading the files from disk is time-consuming.
 
-== Scheduler: logging ==
+=== Logging ===
 
 The contents of the scheduler log file is controlled by the following:
@@ -301 +302 @@
 
 
-== Scheduler: client control == #client-control
+=== Client control === #client-control
 {{{
 <next_rpc_delay>x</next_rpc_delay>
@@ -347 +348 @@
 This is intended for [NonCpuIntensive applications that use little CPU time], e.g. that do network or host measurements.
 
-== Scheduler: deprecated options ==
+=== Deprecated options ===
 
 {{{