Changes between Version 22 and Version 23 of GpuWorkFetch


Ignore:
Timestamp:
Jan 1, 2009, 8:07:43 PM (16 years ago)
Author:
jm7
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GpuWorkFetch

    v22 v23  
    106106 * If P supplies a job for R, D(P,R) is set to true.
    107107 * If we send P a request that doesn't return any jobs, then for each resource R for which req_seconds(R)>0, D(P,R) is set to false.
     108     *** Proposed change.  This could be too sensitive to temporary outages - why not have the project respond with information about whether the resource type is currently supported in some other form than the project currently has work.  This would mean a 3 state response - "Work is returned", "No work, but the resource is supported", and "The resource is not supported".
    108109
    109110=== Per-resource-type backoff ===
     
    117118The backoff interval is doubled up to a limit whenever we ask for work of that type and don't get any work;
    118119it's cleared whenever we get a job of that type.
     120
     121*** Proposed clarification - the overall contact backoff would be the minimum of the backoff for each resource type. 
     122*** Question:  If the project asks for a communications backoff, and one of the resource type backoffs would expire within the project requested backoff, how do we handle that?
     123*** Question:  If we need to contact a project for a tasks of two different types, and one of the backoffs is satisfied, do we ask for both types?
    119124
    120125=== Work-fetch state ===