Changes between Version 4 and Version 5 of LowLatency


Ignore:
Timestamp:
10/03/07 13:22:43 (10 years ago)
Author:
knreed
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • LowLatency

    v4 v5  
    2222{{{<next_rpc_delay>x</next_rpc_delay>}}}
    2323
    24 telling the client when to contact the scheduler again. By varying this value, a project can achieve a rate of connection requests necessary to achieve its latency bounds.  The current BOINC scheduler code has no support for sending this tag, or for figuring out what its value should be. If you want to do low-latency computing, the scheduler must be modified and extended as follows:
     24telling the client when to contact the scheduler again. By varying this value, a project can achieve a rate of connection requests necessary to achieve its latency bounds.  Projects can currently add this tag to the project configuration file to ensure that all clients will perform a RPC no later then X seconds after their last RPC with the project.  In the future it would be nice to expand the capability of this field and make it dynamic.  The following scheduler changes would need to be done:
    2525
    2626 * Keep track of how many active hosts you have (this will change over time).
     
    2828 * Parameterize your workload: how many jobs per batch, latency bound, FLOPs per job, etc.
    2929 * Do the math and write the code for figuring out that the RPC delay should be for a given host (this is dynamic - it will change with the number of active hosts).
    30  * Change the scheduler so that it sends this value in the reply, and so that it sends the appropriate number of jobs.
     30 * Change the scheduler so that it uses this value so that it only sends the appropriate number of jobs.
    3131
    3232If you're interested in helping add these features to BOINC, please [ProjectPeople contact us].