Update comments in bisect/perf bot config file.

tools/run-bisect-perf-regression.cfg

 # Copyright (c) 2013 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.
 
 """Config file for Run Performance Test Bisect Tool
 
 This script is intended for use by anyone that wants to run a remote bisection
 on a range of revisions to look for a performance regression. Modify the config
 below and add the revision range, performance command, and metric. You can then
 run a git try <bot>.
@@ skipping 14 matching lines @@
 
       The metric name is "<graph>/<trace>".
   'repeat_count': The number of times to repeat the performance test.
   'max_time_minutes': The script will attempt to run the performance test
       "repeat_count" times, unless it exceeds "max_time_minutes".
   'truncate_percent': Discard the highest/lowest % values from performance test.
 
 Sample config:
 
 config = {
-  'command': './out/Release/performance_ui_tests' +
-      ' --gtest_filter=PageCyclerTest.Intl1File',
-  'good_revision': '179755',
-  'bad_revision': '179782',
-  'metric': 'times/t',
+  'command': './tools/perf/run_measurement --browser=release blink_perf third_party/WebKit/PerformanceTests/Layout/floats_50_100.html',
+  'good_revision': '233015',
+  'bad_revision': '233115',
+  'metric': 'floats_50_100/floats_50_100',
   'repeat_count': '20',
   'max_time_minutes': '20',
   'truncate_percent': '25',
 }
 
 On Windows:
   - If you're calling a python script you will need to add "python" to
 the command:
 
 config = {
@@ skipping 30 matching lines @@
   'command': '',
   'good_revision': '',
   'bad_revision': '',
   'metric': '',
   'repeat_count':'',
   'max_time_minutes': '',
   'truncate_percent':'',
 }
 
 # Workaround git try issue, see crbug.com/257689