First cut of chrome-proxy (data reduction proxy) measurements.

tools/perf/page_sets/chrome_proxy/bypass.json

Index: tools/perf/page_sets/chrome_proxy/bypass.json
diff --git a/tools/perf/page_sets/chrome_proxy/bypass.json b/tools/perf/page_sets/chrome_proxy/bypass.json
new file mode 100644
index 0000000000000000000000000000000000000000..a13ebb1f0fe0119538495db581a6cacfdf62e792
--- /dev/null
+++ b/tools/perf/page_sets/chrome_proxy/bypass.json
@@ -0,0 +1,13 @@
+{
+  "description": "Chrome proxy test sites",
+  "pages": [
+    {
+      "url": "http://aws1.mdw.la/bypass/",
+      "why": ""
+    },
+    {
+      "url": "http://aws1.mdw.la/piatek/bypass-demo",

[bengr, 2014/03/12 18:17:36]

We should probably make copies of all of these URLs so that the tests don't
break when someone modifies one of them. E.g., we could put them in
aws1.mdw.la/tests/. Also, if we really need to depend on aws, we should have a
domain that isn't mdw.la.

[bolian, 2014/03/19 00:20:03]

Good point. I think we will end up have a dedicated set of pages for telemetry
tests, but for now I just use these.

+      "why": ""
+    }
+  ]
+}