Add bisect-config-trying script and a few example configs.

tools/auto_bisect/configs/win.bisect.blink_perf.cfg

Index: tools/auto_bisect/configs/win.bisect.blink_perf.cfg
diff --git a/tools/auto_bisect/configs/win.bisect.blink_perf.cfg b/tools/auto_bisect/configs/win.bisect.blink_perf.cfg
new file mode 100644
index 0000000000000000000000000000000000000000..13658348c7f3be554ba335234ffb88b92946a865
--- /dev/null
+++ b/tools/auto_bisect/configs/win.bisect.blink_perf.cfg
@@ -0,0 +1,19 @@
+# This config is based on:
+# http://build.chromium.org/p/tryserver.chromium.perf/builders/win_xp_perf_bisect/builds/1197
+# Which found a regression in v8.
+
+config = {
+  'command': 'python tools/perf/run_benchmark -v --browser=release blink_perf.bindings',
+  'good_revision': '300178',
+  'bad_revision': '300184',
+  'metric': 'create-element/create-element',
+  'repeat_count': '2',
+  'max_time_minutes': '5',
+  'truncate_percent': '25',
+  'bug_id': '425581',
+  'gs_bucket': 'chrome-perf',
+  'builder_host': 'master4.golo.chromium.org',
+  'builder_port': '8341',
+}
+
+# Workaround git try issue, see crbug.com/257689