Changes between Version 10 and Version 11 of PrefsPresets


Ignore:
Timestamp:
May 21, 2018, 12:47:59 PM (6 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PrefsPresets

    v10 v11  
     1[[PageOutline]]
    12= Prefs presets =
    23
     
    1011Eventually the Manager should provide the same interface.
    1112
    12 == Proposed presets ==
     13== Defining presets ==
     14
     15Projects can define their own sets of presets.
     16Presets will be stored in a file "prefs_presets.xml" in the project directory,
     17with the structure
     18{{{
     19<presets>
     20   <preset>
     21      <name>Green</name>
     22      <description>Limit power consumption</description>
     23      <prefs>
     24<![CDATA[
     25<max_ncpus_pct>25</max_ncpus_pct>
     26<cpu_usage_limit>100</cpu_usage_limit>
     27...
     28]]>
     29      </prefs>
     30   </preset>
     31   ...
     32</presets>
     33}}}
     34
     35== Default presets ==
     36
     37We'll need to define a default set of presets which ship with the BOINC server code.
     38Proposed default presets:
    1339
    1440=== Max computing ===
     
    2955=== Energy-saver ===
    3056
    31 Compute as energy-efficiently as possible.
     57Compute energy-efficiently; try to maximize FLOPs/watt.
    3258
    3359To implement this properly we need to look at Peter Hannape's work
     
    3662Don't compute while idle; let the computer go into low-power mode or turn off
    3763
    38 == Proposed values ==
     64=== Proposed values ===
    3965
    4066||                                  || Max  || Standard || Green    ||
     
    6187|| upload rate limit kb/sec         || ---  || ---      || ---      ||
    6288
     89== Implementation ==
    6390
    64 == Implementation ==
     91=== Database ===
    6592
    6693If a user selects a preset,
     
    76103</global_preferences>
    77104}}}
    78 The scheduler sends the corresponding prefs in its reply.
    79 This lets us change/extend the meanings of the standard presets,
    80 and lets each project define its own presets if it wants.
    81105
    82 Initial implementation: for simplicity, support only presets.
    83 Enable this by PREFS_PRESETS in project.inc.
    84 
    85 Presets will be stored in a file "prefs_presets.xml" in the project directory,
    86 with the structure
    87 {{{
    88 <presets>
    89    <preset>
    90       <name>Green</name>
    91       <description>Limit power consumption</description>
    92       <prefs>
    93 <![CDATA[
    94 <max_ncpus_pct>25</max_ncpus_pct>
    95 <cpu_usage_limit>100</cpu_usage_limit>
    96 ...
    97 ]]>
    98       </prefs>
    99    </preset>
    100    ...
    101 </presets>
    102 }}}
    103 
     106=== Scheduler ===
    104107Scheduler: when sending global prefs, check if it's a preset and expand accordingly.
    105108Also send the preset name in case we want to show it in the Manager.
     109
     110=== Web ===
     111If enabled ('''<prefs_presets/>''' in config.xml)
     112the web interface for prefs would show radio buttons for the presets,
     113with a "customize" option that would expose the current interface.
     114
     115=== Manager ===
     116
     117This is farther off, but eventually the Manager (advanced, simple, Android) could
     118offer presets, with the option to customize.