Update and standardize example experiment files.

This cleans up the example experiment files, makes sure they are
all up to date, and that they use consisten wording and examples
throughout.  It also renames  some of them.

BUG=None
TEST=None

Change-Id: I1bbf9e364a0dfae7cfb880011f2c140e1a347e98
Reviewed-on: https://chrome-internal-review.googlesource.com/161386
Reviewed-by: Yunlian Jiang <yunlian@google.com>
Commit-Queue: Caroline Tice <cmtice@google.com>
Tested-by: Caroline Tice <cmtice@google.com>

1 files changed, 45 insertions, 0 deletions

diff --git a/crosperf/experiment_files/page_cycler_perf.exp b/crosperf/experiment_files/page_cycler_perf.exp
new file mode 100644
index 00000000..f3f962b3
--- /dev/null
+++ b/crosperf/experiment_files/page_cycler_perf.exp
@@ -0,0 +1,45 @@
+# This experiment profiles some of the Telemetry page cycler tests,
+# uisng 'perf' on the remotes to get performance profiles.
+#
+# You should replace all the placeholders, marked by angle-brackets,
+# with the appropriate actual values.
+
+name: aes_example
+board: <your-board-goes-here>
+
+# Note:  You can specify multiple remotes, to run your tests in parallel on
+# multiple machines. e.g. "remote: test-machine-1.com test-machine2.come
+# test-machine3.com"
+remote: <your-remote-goes-here>
+
+perf_args: record -e cycles,instructions
+
+benchmark: page_cycler.morejs {
+	suite: telemetry_Crosperf
+	iterations: 10
+}
+
+benchmark: page_cycler.bloat {
+	suite: telemetry_Crosperf
+	iterations: 10
+}
+
+benchmark: page_cycler.dhtml {
+	suite: telemetry_Crosperf
+	iterations: 10
+}
+
+benchmark: page_cycler.intl_ar_fa_he {
+	suite: telemetry_Crosperf
+	iterations: 10
+}
+
+benchmark: page_cycler.moz {
+	suite: telemetry_Crosperf
+	iterations: 10
+}
+
+# Replace the chromeos image below with the actual path to your test image.
+test_image {
+  chromeos_image:<path-to-your-chroot>/src/build/images/<board>/test-image/chromiumos_test_image.bin
+}