All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=741715

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=39f6565cb7540a9ea4e80216e0833ea26db93ffb49dd863a9a4ef1ada63d0def


Bot(s) for this bug's original alert(s):

chromium-rel-win7-dual

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8974256718767729616

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 6283b4ab74ed60be4f736b483bb641bab94ffb2d
  bad_revision : 1b8aa25347a0c404ed7600ee4f564aea7d80f4fc

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : blink_perf.parser
  Metric       : query-selector-id-deep/query-selector-id-deep

Revision             Result                  N
chromium@484959      60747.3 +- 1710.41      21      good
chromium@484988      60634.0 +- 2432.03      21      good
chromium@485003      60579.3 +- 2936.43      14      good
chromium@485011      60574.9 +- 1502.89      21      good
chromium@485017      60170.7 +- 1712.51      14      bad
chromium@485075      60329.8 +- 1491.89      14      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.parser

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8974256718767729616


For feedback, file a bug with component Speed>Bisection

This came back down.