Remove all MemoryModel-related code, since we're unlikely to use it again. Also changes some sample code to use a random generic name ("PruningAlgorithm") instead of MemoryModel in hopes that no one will be confused.
This does not remove IdleTimer, even though it now has no users. I do plan to remove it, but I want to do that in a separate commit so it's easy to reference and revert if at some later point we want this functionality.
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/242079
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@27652 0039d316-1c4b-4281-b951-d872f2087c98
diff --git a/base/field_trial.h b/base/field_trial.h
index 82bf3b36..0779981 100644
--- a/base/field_trial.h
+++ b/base/field_trial.h
@@ -22,7 +22,7 @@
//------------------------------------------------------------------------------
// Example: Suppose we have an experiment involving memory, such as determining
-// the impact of memory model command line flags actual memory use.
+// the impact of some pruning algorithm.
// We assume that we already have a histogram of memory usage, such as:
// HISTOGRAM_COUNTS("Memory.RendererTotal", count);
@@ -38,9 +38,9 @@
// int group2 = trial->AppendGroup("_low_mem", 20); // 2% in _low_mem group.
// // Take action depending of which group we randomly land in.
// if (trial->group() == group1)
-// SetMemoryModel(HIGH); // Sample setting of browser state.
+// SetPruningAlgorithm(kType1); // Sample setting of browser state.
// else if (trial->group() == group2)
-// SetMemoryModel(LOW); // Sample alternate setting.
+// SetPruningAlgorithm(kType2); // Sample alternate setting.
// We then modify any histograms we wish to correlate with our experiment to
// have slighly different names, depending on what group the trial instance
