Changes between Version 22 and Version 23 of ProjectOptions

Timestamp:

Jun 2, 2007, 6:52:12 AM (17 years ago)

Author:

davea

Comment:

--

ProjectOptions

@@ -58 +58 @@
         If the scheduling server has no work, it replies to RPCs without doing any database access (e.g., without looking up the user or host record). This reduces DB load, but it fails to update preferences when users click on Update. Use it if your server DB is overloaded.
  '''resend_lost_results'''::
-        If set, and a <other_results> list is present in scheduler request, resend any in-progress results not in the list. This is recommended; it may increase the efficiency of your project. For reasons that are not well understood, a BOINC client sometimes fails to receive the scheduler reply. This flag addresses that issue: it causes the SAME results to be resent by the scheduler, if the client has failed to receive them.  Note: this will increase the load on your DB server.
+        If set, and a <other_results> list is present in scheduler request, resend any in-progress results not in the list. This is recommended; it may increase the efficiency of your project. For reasons that are not well understood, a BOINC client sometimes fails to receive the scheduler reply. This flag addresses that issue: it causes the SAME results to be resent by the scheduler, if the client has failed to receive them.  Note: this will increase the load on your DB server; you can minimize this by creating an index:
+{{{
+alter table result add index res_host_state (hostid, server_state);
+}}}
  '''send_result_abort'''::
         If set, and the client is processing a result for a WU that has been cancelled or is not in the DB (i.e. there's no chance of getting credit) send <result_abort>. If client is processing a result for a WU that has been assimilated or is overdue (i.e. there's a chance of not getting credit) send <result_abort_if_not_started>. Note: this will increase the load on your DB server.