Set new baseline for benchmark metrics
Set new baseline for benchmark metrics

Make the benchmarks more closely resemble real world usage. Users don't
search for "foobar" but rather "f", then "fo", then "foo" etc (unless
they have debouncing turned on).

I have some optimizations planned to handle exactly this case, so I'm
adjusting the benchmark so that I can measure the impact of the change.

I could have tweaked the `times` value of any of the benchmarks except
for "chromium (whole)" (which is already at 1), but I figured they're
all shorter anyway so they may as well just stay as they are.

New baseline:

                          user     system      total        real
  pathological        3.640000   0.090000   3.730000 (  3.805231)
  command-t           2.170000   0.030000   2.200000 (  2.209098)
  chromium (subset)   2.600000   0.220000   2.820000 (  1.626648)
  chromium (whole)   12.340000   0.060000  12.400000 (  7.209598)

wincent/command-t,mtimkovich/command-t,wincent/command-t,yrro/command-t,yrro/command-t,wincent/command-t,mtimkovich/command-t