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

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


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

android-webview-nexus5X

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : rasterize_and_record_micro.top_25
  Metric       : record_time/file___static_top_25_wordpress.html

Revision             Result                       N
chromium@514571      0.0446667 +- 0.00216025      21      good
chromium@514641      0.0444762 +- 0.00269037      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=file...static.top.25.wordpress.html rasterize_and_record_micro.top_25

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

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


For feedback, file a bug with component Speed>Bisection

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

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

Hi wkorman@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 : Walter Korman
  Commit : db0e590542ca41876ea92d6b9413073e9fb0ef46
  Date   : Tue Nov 07 02:12:29 2017
  Subject: Update static snapshot for majority of top 25 sites.

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : rasterize_and_record_micro.top_25
  Metric       : record_time/file___static_top_25_wordpress.html
  Change       : 48.09% | 0.0305 -> 0.0451666666667

Revision             Result                        N
chromium@514000      0.0305 +- 0.00122474          6      good
chromium@514350      0.0306667 +- 0.00182574       6      good
chromium@514356      0.0303333 +- 0.0011547        6      good
chromium@514357      0.0448333 +- 0.000912871      6      bad       <--
chromium@514358      0.044 +- 1.69967e-17          6      bad
chromium@514359      0.0441667 +- 0.000912871      6      bad
chromium@514361      0.044 +- 0.00141421           6      bad
chromium@514372      0.045 +- 1.69967e-17          6      bad
chromium@514394      0.0448333 +- 0.000912871      6      bad
chromium@514438      0.0451667 +- 0.00219848       6      bad
chromium@514525      0.0455 +- 0.00122474          6      bad
chromium@514700      0.0451667 +- 0.000912871      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=file...static.top.25.wordpress.html rasterize_and_record_micro.top_25

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

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


For feedback, file a bug with component Speed>Bisection

Transferring these to vmpstr@ as owner of the involved benchmark.

Note that the r_and_r benchmark is in consideration to be replaced (for perf regression monitoring purposes at least) by an updated repaint benchmark. More on that at issue 770800.

vmpstr: any update on this bug?

According to pinpoint this is a change as a result of updating pagesets. If that's the case this should be considered the new "norm" for the tests. Please re-open if you disagree.