Changes between Version 5 and Version 6 of LocalityScheduling


Ignore:
Timestamp:
07/21/14 23:03:24 (3 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • LocalityScheduling

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