Changes between Version 3 and Version 4 of ClientSchedOctTen

Timestamp:

Oct 26, 2010, 2:07:49 PM (14 years ago)

Author:

davea

Comment:

--

ClientSchedOctTen

@@ -13 +13 @@
 The current policies, described [GpuWorkFetch here],
 maintain long- and short-term debts for each
-(project, resource type) pair.
+(project, processor type) pair.
 
-Job scheduling for a given resource type is based on STD.
-Projects with greater STD for the resource are given priority.
+Job scheduling for a given processor type is based on STD.
+Projects with greater STD for the type are given priority.
 
 Work fetch is based on a weighted sum of LTDs.
 Work is typically fetched from the project for which this sum is greatest,
-and typically work is requested for all resource types.
+and typically work is requested for all processor types.
 
 These policies fail to meet their goals in many cases.
@@ -49 +49 @@
 === The bottom line ===
 
-The current approach - extending the STD/LTD model to multiple resource types -
+The current approach - extending the STD/LTD model to multiple processor types -
 seemed good at the time but turns out to be the wrong way.