Changes between Version 37 and Version 38 of ProjectOptions

Timestamp:

Sep 6, 2007, 8:07:51 AM (17 years ago)

Author:

maire

Comment:

--

ProjectOptions

@@ -81 +81 @@
  '''default_disk_min_free_gb'''::
         Sets the default value for the `disk_min_free_gb` preference so its consistent between the scheduler and web pages. The scheduler uses it when a request for work doesn't include preferences. The web page scripts use it to set the initial value when displaying or editing preferences the first time, or when the user never saved them. Also, the scheduler uses this setting to override any smaller preference from the host, it enforces a 'minimum free disk space' to keep from filling up the drive. Recommend setting this no smaller than .001 (1MB or 1,000,000 bytes). Default is .001.
- '''reliable_min_avg_credit, reliable_min_avg_turnaround'''::
+ '''reliable_min_avg_credit, reliable_max_avg_turnaround'''::
         Hosts for which `expavg_credit`/`ncpus` is at least `reliable_min_avg_credit` and whose average turnaround is at most reliable_max_avg_turnaround are considered 'reliable'.
  '''reliable_time, reliable_reduced_delay_bound'''::
         When the age of a workunit exceeds reliable_time (typically 2-3X the delay bound), send results only to reliable hosts, and multiply the delay bound by reliable_reduced_delay_bound (typically 0.5 or so).
  '''reliable_on_priority, reliable_on_over, reliable_on_over_except_error'''::
-        Results with priority at least 'reliable_on_priority' will be sent only to reliable hosts; increase priority of duplicate results by 'reliable_on_over'; increase priority of duplicates caused by timeout (not error) by 'reliable_on_over_except_error'.
+        Results with priority at least 'reliable_on_priority' will be sent only to reliable hosts; increase priority of duplicate results by 'reliable_priority_on_over'; increase priority of duplicates caused by timeout (not error) by 'reliable_priority_on_over_except_error'.
  '''one_result_per_host_per_wu'''::
         If present, send at most one result of a given workunit to a given host. This is weaker than `one_result_per_user_per_wu`; it is useful if you're using homogeneous redundancy and most of the hosts of a particular class belong to a single user.