Changes between Version 6 and Version 7 of PrefsPresets

Timestamp:

Sep 26, 2017, 11:37:19 PM (7 years ago)

Author:

davea

Comment:

--

PrefsPresets

@@ -39 +39 @@
 
 ||                                  || Max  || Standard || Green    ||
-|| use at most X% of CPUs           || 100  || 85       || 85       ||
+|| use at most X% of CPUs           || 100  || 85       || 60       ||
 || use at most X% of CPU time       || 100  || 100      || 100      ||
 || suspend when on battery          || yes  || yes      || yes      ||
@@ -56 +56 @@
 || when in use, use < X% RAM        || 70   || 50       || 50       ||
 || when not in use, use < X% RAM    || 90   || 90       || 90       ||
-|| leave non-GPU tasks in mem       || no   || no       || no       ||
+|| leave non-GPU tasks in mem       || yes  || no       || no       ||
 || use at most X% swap file         || 75   || 75       || 75       ||
 || download rate limit kb/sec       || ---  || ---      || ---      ||
@@ -64 +64 @@
 == Implementation ==
 
-If a user selects one of these,
+If a user selects a preset,
 we should store the preset name (max, standard, green) in user.global_prefs,
 rather than the prefs themselves.
-Examples:
+Example:
 {{{
 <global_preferences>
@@ -79 +79 @@
 This will let us change/extend the meanings of the presets.
 
-Users can still edit any pref.
-But if they change anything, they're not using the preset anymore.
-
+Initial implementation: for simplicity, support only presets.
 Enable this by PREFS_PRESETS in project.inc.
 
-If set:
-- default new accounts to "standard"
+PHP code only needs to know about preset names.
 
-In any case:
-- scheduler: expand <preset>foo</preset> to appropriate XML.
+C++ code