Changes between Version 16 and Version 17 of CreditNew


Ignore:
Timestamp:
Nov 16, 2009, 12:26:40 PM (15 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CreditNew

    v16 v17  
    643643== Trickle credit ==
    644644
     645CPDN breaks jobs into segments,
     646sends a trickle-up message for each segment,
     647and grants credit for each completed segment.
     648In this case,
     649the trickle message handlers should not grant a fixed amount of credit.
     650Instead, the trickle-up messages should contain
     651an "incremental elapsed time" field.
    645652
    646653== Job runtime estimates ==
     
    656663
    657664
    658 == Error rate,host punishment, and turnaround time estimation ==
     665== Error rate, host punishment, and turnaround time estimation ==
    659666
    660667Unrelated to the credit proposal, but in a similar spirit.
     
    665672Similar for turnaround time.
    666673
    667 The host punishment mechanism is designed to
    668 deal with malfunctioning hosts.
     674So we'll move the "error_rate" and "turnaround_time"
     675fields from the host table to host_app_version.
     676
     677The host punishment mechanism is designed to deal with malfunctioning hosts.
    669678For each host the server maintains '''max_results_day'''.
    670679This is initialized to a project-specified value (e.g. 200)
     
    675684result is received.
    676685
    677 So we'll move the "error_rate", "turnaround_time"
    678 and "max_results_day" fields from the host table to host_app_version.
     686This should also be per-app-version,
     687so we'll move "max_results_day" from the host table to host_app_version.
    679688
    680689== Cherry picking ==
     
    713722only if there's solid evidence that the host is NOT cherry picking.
    714723
     724Because this mechanism is punitive to hosts
     725that experience actual failures,
     726we'll make it selectable on a per-application basis (default off).
     727
    715728In addition, to limit the extent of cheating
    716729(in case the above mechanism is defeated somehow)
    717 the host scaling factor will be min'd with a configurable parameters (say, 3).
     730the host scaling factor will be min'd with a
     731project-wide config parameter (default, say, 3).
    718732
    719733== Implementation ==