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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgxvOkhQkM


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

linux-release

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

=== Auto-CCing suspected CL author wangxianzhu@chromium.org ===

Hi wangxianzhu@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Xianzhu Wang
  Commit : a16e62c523aac46945d3782fea8bda79247879d9
  Date   : Sat May 27 21:35:01 2017
  Subject: Reland Don't access DisplayItemClient::VisualRect() for cached display items.

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : rasterize_and_record_micro.top_25
  Metric       : record_time/record_time
  Change       : 3.56% | 0.0713263888889 -> 0.0738680555556

Revision             Result                        N
chromium@475248      0.0713264 +- 0.000741659      6      good
chromium@475250      0.0714028 +- 0.000320951      6      good
chromium@475251      0.0738819 +- 0.000557202      6      bad       <--
chromium@475253      0.0738681 +- 0.000345691      6      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 rasterize_and_record_micro.top_25

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8977589623721182064

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5843571657146368


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

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

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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Xianzhu Wang
  Commit : a16e62c523aac46945d3782fea8bda79247879d9
  Date   : Sat May 27 21:35:01 2017
  Subject: Reland Don't access DisplayItemClient::VisualRect() for cached display items.

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : rasterize_and_record_micro.top_25
  Metric       : record_time/http___www.ebay.com
  Change       : 3.37% | 0.0543333333333 -> 0.0561666666667

Revision             Result                        N
chromium@475248      0.0543333 +- 0.0011547        6      good
chromium@475250      0.0543333 +- 0.0011547        6      good
chromium@475251      0.0561667 +- 0.000912871      6      bad       <--
chromium@475253      0.0561667 +- 0.000912871      6      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 --story-filter=http...www.ebay.com rasterize_and_record_micro.top_25

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8976655679250046320

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6590833588961280


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Xianzhu Wang
  Commit : a16e62c523aac46945d3782fea8bda79247879d9
  Date   : Sat May 27 21:35:01 2017
  Subject: Reland Don't access DisplayItemClient::VisualRect() for cached display items.

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : rasterize_and_record_micro.top_25
  Metric       : record_time/https___www.google.com__hl_en_q_barack+obama
  Change       : 3.15% | 0.0332857142857 -> 0.0343333333333

Revision             Result                       N
chromium@475248      0.0332857 +- 0.0029761       14      good
chromium@475250      0.0333333 +- 0.00282843      9       good
chromium@475251      0.0343333 +- 0.0011547       6       bad       <--
chromium@475253      0.0343333 +- 0.00141421      9       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 --story-filter=https...www.google.com..hl.en.q.barack.obama rasterize_and_record_micro.top_25

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8976655718125088944

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=4746708648460288


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

I would like to accept this.