Changes between Version 25 and Version 26 of CreditNew

Timestamp:

Mar 25, 2010, 10:17:58 AM (15 years ago)

Author:

davea

Comment:

--

CreditNew

@@ -34 +34 @@
 
  * Project neutrality: different projects should grant
-   about the same amount of credit per day for a given processor.
+   about the same amount of credit per host,
+   averaged over all hosts.
+
+ * Cheat-proof
 
 It's easy to show that both goals can't be satisfied simultaneously.
@@ -412 +415 @@
 === Database changes ===
 
-New table '''host_app''':
+New table '''host_app_version''':
 {{{
 int    host_id;
-int    app_id;
-int    vnpfc_n;
-double vnpfc_sum;
-double vnpfc_exp_avg;
-}}}
-
-New table '''host_app_version''':
-{{{
-int    host_id;
-int    app_version_id;
-int    et_n;
-double et_sum;
-double et_exp_avg;
-// some variable for recent error rate,
-// replacing host.error_rate and host.max_results_day
-// make sure that a host w/ 1 good and 1 bad GPU gets few GPU jobs
+int    app_version_id;          // generalized for anon platform
+AVERAGE pfc;
+AVERAGE_VAR et;                         // elapsed time / wu.rsc_fpops_est
+double host_scale_time;
+bool scale_probation;
+double error_rate;
+int max_jobs_per_day;
+int n_jobs_today;
+AVERAGE_VAR turnaround;
 }}}
 
 New fields in '''app_version''':
 {{{
-int    pfc_n;
-double pfc_sum;
-double pfc_exp_avg;
-double pfc_scaling_factor;
+AVERAGE pfc;
+double pfc_scale;
+double expavg_credit;
+double expavg_time;
 }}}
 
 New fields in '''app''':
 {{{
-int    vnpfc_n;
-double vnpfc_sum;
-double vnpfc_exp_avg;
-}}}
-
-=== New request message fields ===
-
-=== New reply message fields ===
+double min_avg_pfc;
+bool host_scale_check;          // whether to do scale probation
+int max_jobs_in_progress;
+int max_gpu_jobs_in_progress;
+int max_jobs_per_rpc;
+int max_jobs_per_day_init;
+}}}
 
 === Scheduler changes ===
 
-=== Client changes ===
+ * When dispatch anonymous app job,
+   set result.app_version_id to -2/-3/-4 depending on resource.
+ * update host_app_version.host_scale_time for
+   app versions for which jobs are being sent
+   and for which scale_probation is set.
 
 === Validator changes ===
 
-=== Server APIs for computing and granting credit ===
-
-== Compatibility ==
-
-
-
+ * To reduce DB access, validator maintains a vector of app_versions.
+   This is appended to by assign_credit_set().
+   At the start of every validator pass, the pfc and expavg_credit
+   fields of the app versions are saved.
+   Updates are accumulated,
+   and at the end of the validator pass (before sleep())
+   the incremental changes are written to the DB.
+   This scheme works correctly even with multiple validators per app.
+ * The updating of app_versions is done in such a way that
+   we pick up changes to pfc_scale by the feeder.
+ * The app record is reread at the start of each scan,
+   in case its min_avg_pfc has been changed by the feeder.
+ * check_set() no longer returns credit (leave arg there for now)
+ * update host_app_version.scale_probation in is_valid()
+ * don't grant credit in is_valid()
+ * compute and grant credit in handle_wu()
+
+=== Feeder changes ===
+
+ * If we're the "main feeder" (mod = 0, or mod not used),
+   update app_version.pfc_scale and app.min_avg_pfc every 10 minutes.