Adding a test for measuring memory usage.

tools/perf/perf_tools/memory_benchmark.py

Index: tools/perf/perf_tools/memory_benchmark.py
diff --git a/tools/perf/perf_tools/memory_benchmark.py b/tools/perf/perf_tools/memory_benchmark.py
new file mode 100644
index 0000000000000000000000000000000000000000..93f04a14346c3cd5f649645732adf87fe6c67f2b
--- /dev/null
+++ b/tools/perf/perf_tools/memory_benchmark.py
@@ -0,0 +1,49 @@
+# Copyright (c) 2012 The Chromium Authors. All rights reserved.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+import copy
+
+from chrome_remote_control import interaction
+from chrome_remote_control import multi_page_benchmark
+from chrome_remote_control import test_helper_interaction #pylint: disable=W0611
+
+MEMORY_HISTOGRAMS = [
+    {'name': 'V8.MemoryExternalFragmentationTotal', 'units': 'percent'},
+    {'name': 'V8.MemoryHeapSampleTotalCommitted', 'units': 'kb'},
+    {'name': 'V8.MemoryHeapSampleTotalUsed', 'units': 'kb'}]
+
+class MemoryBenchmark(multi_page_benchmark.MultiPageBenchmark):
+  def __init__(self):
+    super(MemoryBenchmark, self).__init__()
+    self._interactions = []
+    self._results = {}
+
+  @staticmethod
+  def GetMemoryHistograms(tab, results):
+    for histogram in MEMORY_HISTOGRAMS:
+      name = histogram['name']
+      data = tab.runtime.Evaluate(
+          'window.domAutomationController.getHistogram("%s")' % name)
+      results.Add(name, histogram['units'], data, data_type='histogram')
+
+  def CustomizeBrowserOptions(self, options):
+    options.extra_browser_args.append('--dom-automation')

[nduca, 2012/11/08 22:05:45]

is this flag considered to be long-term supported? Does it work in clank? Is
this something slated to be deleted once we purge our architecture of pyauto/ui
tests?

[marja, 2012/11/09 14:17:35]

The --dom-automation command line switch is ultimately processed by
RenderViewImpl, so it should be supported by clank as well. It's not necessarily
going to exist forever, but we need to somehow keep the histogram fetching
working (for the normal page cyclers which already produce memory histograms),
and afaics, the approach will be the same in the future (i.e., pass chrome a
command line switch which makes it export a JavaScript objects through which the
histograms can be retrieved).

+
+  def DoNextInteraction(self, page, tab):

[nduca, 2012/11/06 05:10:02]

I'd like to see interactions be part of the multi_page_runner rather than part
of the benchmark.

[marja, 2012/11/09 14:17:35]

Now that we have compound interactions, running the interactions is simpler. Can
you have a look at the latest version?

If the benchmark is the one that executes the interaction, it can know which one
of them to execute, i.e., memory_benchmark.py hard-codes that the interaction to
execute is "stress_memory". If I move the interaction execution to some other
place, I'd need to retrieve the "what interaction to execute" from the test, and
pass it around...

+    if not self._interactions:
+      return False
+    data = self._interactions[0]
+    self._interactions = self._interactions[1:]
+    i = interaction.FindClassWithName('TestHelper')(data)
+    i.PerformInteraction(page, tab, self)
+    return True
+
+  def DidPerformInteraction(self, _, page, tab):
+    if not self.DoNextInteraction(page, tab):
+      self.GetMemoryHistograms(tab, self._results)
+
+  def MeasurePage(self, page, tab, results):
+    self._interactions = copy.copy(page.interactions)
+    self._results = results
+    tab.WaitForDocumentReadyStateToBeComplete()
+    self.DoNextInteraction(page, tab)