Changes between Version 16 and Version 17 of CreditNew

Timestamp:

Nov 16, 2009, 12:26:40 PM (15 years ago)

Author:

davea

Comment:

--

CreditNew

@@ -643 +643 @@
 == Trickle credit ==
 
+CPDN breaks jobs into segments,
+sends a trickle-up message for each segment,
+and grants credit for each completed segment.
+In this case,
+the trickle message handlers should not grant a fixed amount of credit.
+Instead, the trickle-up messages should contain
+an "incremental elapsed time" field.
 
 == Job runtime estimates ==
@@ -656 +663 @@
 
 
-== Error rate,host punishment, and turnaround time estimation ==
+== Error rate, host punishment, and turnaround time estimation ==
 
 Unrelated to the credit proposal, but in a similar spirit.
@@ -665 +672 @@
 Similar for turnaround time.
 
-The host punishment mechanism is designed to
-deal with malfunctioning hosts.
+So we'll move the "error_rate" and "turnaround_time"
+fields from the host table to host_app_version.
+
+The host punishment mechanism is designed to deal with malfunctioning hosts.
 For each host the server maintains '''max_results_day'''.
 This is initialized to a project-specified value (e.g. 200)
@@ -675 +684 @@
 result is received.
 
-So we'll move the "error_rate", "turnaround_time"
-and "max_results_day" fields from the host table to host_app_version.
+This should also be per-app-version,
+so we'll move "max_results_day" from the host table to host_app_version.
 
 == Cherry picking ==
@@ -713 +722 @@
 only if there's solid evidence that the host is NOT cherry picking.
 
+Because this mechanism is punitive to hosts
+that experience actual failures,
+we'll make it selectable on a per-application basis (default off).
+
 In addition, to limit the extent of cheating
 (in case the above mechanism is defeated somehow)
-the host scaling factor will be min'd with a configurable parameters (say, 3).
+the host scaling factor will be min'd with a
+project-wide config parameter (default, say, 3).
 
 == Implementation ==