Changes between Version 5 and Version 6 of LocalityScheduling

Timestamp:

Jul 21, 2014, 11:03:24 PM (10 years ago)

Author:

davea

Comment:

--

LocalityScheduling

@@ -11 +11 @@
 
 To use locality scheduling you must declare the large input files as
-[JobSubmission#Inputtemplatefiles sticky].
+[JobTemplates sticky] (so they're not deleted on the client)
+and [JobTemplates no_delete] (so they're not deleted on the server).
 
 There are two variants of locality scheduling:
@@ -18 +19 @@
   fairly small (of order 100).
  * '''Standard''': use in other cases.
-  Note: this hasn't been implemented yet.
-  A design document is [LocalityNew here].
+  A highly project-specific version of this is used by Einstein@home.
+  A more general version has been [LocalityNew designed]
+ but is not yet implemented.
 
 == Limited locality scheduling ==
@@ -25 +27 @@
 Limited locality scheduling (LLS) uses BOINC's standard share-memory job cache scheduling mechanism.
 It assumes that the ratio of the job cache size to the number of data files
-is sufficiently large that, on average, there is at least one job
+is sufficiently large that there is usually at least one job
 in the cache for a given data file.
 It dispatches jobs that use files resident on the client
@@ -44 +46 @@
 and the policy won't work well.
 
-Currently there is no mechanism for deleting old, unused sticky files from clients.
-We'll need to add one at some point.
+When you have no more jobs for an input file,
+you can [DeleteFile arrange for it to be deleted from clients].