Changes between Version 6 and Version 7 of CreditOptions


Ignore:
Timestamp:
Jul 18, 2018, 4:56:41 PM (4 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CreditOptions

    v6 v7  
    8686Runtime-based credit is limited by max_granted_credit, but is otherwise not cheat-proof.
    8787
     88== Runtime-based credit via trickle messages ==
     89
     90If you have very long-running jobs (a week or more) you may want to
     91grant credit incrementally.
     92To do so:
     93
     94 * Have your application periodically send [TrickleApi trickle-up messages]
     95  with variety '''runtime''' and content
     96{{{
     97<runtime>X</runtime>
     98}}}
     99  where X is the runtime since the last trickle message.
     100
     101 * Run the '''trickle_credit''' daemon as follows:
     102{{{
     103trickle_credit --variety runtime --max_runtime Y
     104}}}
     105where Y is the limit on runtime
     106(typically the period of the trickle messages).
     107
     108 * Run your validator for the app with the '''--no_credit''' option
     109
     110The '''trickle_credit''' daemon grants credit in proportion to (runtime * CPU FLOPS),
     111hence this approach should be used only for applications with only single-CPU versions.
     112
     113This approach is not device-neutral because hosts with the same peak FLOPS
     114may have different actual FLOPS for the app version.
     115
    88116== Adaptive credit ==
    89117