[tools/perf] Remove remaining references to indexeddb_perf benchmark

tools/perf/docs/perf_bot_sheriffing.md

 # Perf Bot Sheriffing
 
 The perf bot sheriff is responsible for keeping the bots on the chromium.perf
 waterfall up and running, and triaging performance test failures and flakes.
 
 **[Rotation calendar](https://calendar.google.com/calendar/embed?src=google.com_2fpmo740pd1unrui9d7cgpbg2k%40group.calendar.google.com)**
 
 ## Key Responsibilities
 
 *   [Handle Device and Bot Failures](#Handle-Device-and-Bot-Failures)
@@ skipping 326 matching lines @@
         2.  See 'Reproducing the task locally' on swarming task page
         3.  First run the command under
             'Download input files into directory foo'
         4.  cd into foo/out/Release if those downloaded inputs
         5.  Execute test from this directory.  Command you are looking for
             should be at the top of the logs, you just need to update the
             `--isolated-script-test-output=/b/s/w/ioFB73Qz/output.json` and
             `--isolated-script-test-chartjson-output=/b/s/w/ioFB73Qz/chartjson-output.json`
             flags to be a local path
         6.  Example with tmp as locally created dir:
-            `/usr/bin/python ../../testing/scripts/run_telemetry_benchmark_as_googletest.py ../../tools/perf/run_benchmark indexeddb_perf -v --upload-results --output-format=chartjson --browser=release --isolated-script-test-output=tmp/output.json --isolated-script-test-chartjson-output=tmp/chartjson-output.json`
+            `/usr/bin/python ../../testing/scripts/run_telemetry_benchmark_as_googletest.py ../../tools/perf/run_benchmark memory.desktop -v --upload-results --output-format=chartjson --browser=release --isolated-script-test-output=tmp/output.json --isolated-script-test-chartjson-output=tmp/chartjson-output.json`

[perezju, 2017/03/31 12:18:25]

Ned, any other suggestion for a benchmark name to use in the example? Was trying
to find something that is likely to last after the upcoming slimming down, and
hopefully not too difficult to run.

[nednguyen, 2017/03/31 12:20:07]

speedometer is easy to run

     *   ssh into swarming bot and run test on that machine
         1.  NOTE: this should be a last resort since it will cause a fifth of
             the benchmarks to continuously fail on the waterfall
         2   First you need to decommission the swarming bot so other jobs don’t
             interfere, file a ticket with go/bugatrooper
         3.  See [remote access to bots](https://sites.google.com/a/google.com/chrome-infrastructure/golo/remote-access?pli=1)
             on how to ssh into the bot and then run the test.
             Rough overview for build161-m1
             *   prodaccess --chromegolo_ssh
             *   Ssh build161-m1.golo
@@ skipping 118 matching lines @@
 
 There is also a weekly debrief that you should see on your calendar titled
 **Weekly Speed Sheriff Retrospective**. For this meeting you should prepare
 any highlights or lowlights from your sheriffing shift as well as any other
 feedback you may have that could improve future sheriffing shifts.
 
 <!-- Unresolved issues:
 1. Do perf sheriffs watch the bisect waterfall?
 2. Do perf sheriffs watch the internal clank waterfall?
 -->