Describe performance monitoring in README.

README.md

Index: README.md
diff --git a/README.md b/README.md
index 46192e6bc2d5ed032620c97d4623c53ad283131b..f358234d068a9e04b1572fb8256dd721e6e15854 100644
--- a/README.md
+++ b/README.md
@@ -289,5 +289,31 @@ To land a change after receiving LGTM:
 $ git cl land
 ```
 
-Don't break the build! Waterfall is here:
-http://build.chromium.org/p/client.mojo/waterfall
+## Monitoring
+
+Our [waterfall](http://build.chromium.org/p/client.mojo/waterfall) continuously
+builds and tests the code. Don't break the build!
+
+### Benchmarks
+
+One of the bots, [Mojo Linux Perf](http://build.chromium.org/p/client.mojo/builders/Mojo%20Linux%20Perf)
+runs a [suite of benchmarks](mojo/tools/data/benchmarks) and uploads the results
+to [performance dashboard](https://chromeperf.appspot.com/). You can browse the

[tonyg, 2015/11/09 17:42:58]

Add "the" or "a" before performance dashboard.

[ppi, 2015/11/10 10:29:18]

Done.

+results [here](https://chromeperf.appspot.com/report), putting `mojo_benchmarks`
+as the "test suite".
+
+Automated alerts about performance regressions are sent to
+[mojo-perf-alerts@chromium.org](https://groups.google.com/a/chromium.org/forum/#!forum/mojo-perf-alerts).
+
+For examples of interesting sets of graphs see:
+
+ - [app
+   startup](https://chromeperf.appspot.com/report?sid=4848464df5ca8467770d80b309740ef56fbff00e773c2c53816fd8bff1fda1e0)
+ - [ipc
+   performance](https://chromeperf.appspot.com/report?sid=9abc20b46f6f8d908b0f07847f1d42eab54c7025a098336e6dc2d3e2030d66f8)
+
+To run the benchmarks locally build Mojo and then run:

[tonyg, 2015/11/09 17:42:57]

Since this section is about monitoring, it seems instructions for running
locally belong up in the "buildmojo" section next to where it talks about
running unittests.

[ppi, 2015/11/10 10:29:18]

Done.

+
+```sh
+mojo/devtools/common/mojo_benchmark mojo/tools/data/benchmarks [--android]
+```