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

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


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

android-webview-nexus6

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

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

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : rasterize_and_record_micro.top_25
  Metric       : rasterize_time/file___static_top_25_booking.html

Revision             Result                  N
chromium@526672      27.3988 +- 1.47769      21      good
chromium@526694      27.4676 +- 1.26602      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.booking.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/8957788006326963744


For feedback, file a bug with component Speed>Bisection

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

Kicked new bisect.

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : rasterize_and_record_micro.top_25
  Metric       : rasterize_time/file___static_top_25_booking.html
  Change       : 1.31% | 27.3522142857 -> 27.6112857143

Suspected Commit Range
  5 commits in range
  https://chromium.googlesource.com/chromium/src/+log/b9a599c21b63d11163b52693e59b777d82932953..e5d92d3149e5e19e7bcb65ec0d27d3c610b976dd


Revision             Result                   N
chromium@526672      27.3522 +- 0.824399      14       good
chromium@526674      27.5811 +- 2.01381       14       good
chromium@526675      ---                      ---      build failure
chromium@526676      ---                      ---      build failure
chromium@526677      ---                      ---      build failure
chromium@526678      ---                      ---      build failure
chromium@526679      27.6206 +- 1.23823       21       bad
chromium@526683      27.6713 +- 1.64224       21       bad
chromium@526694      27.6113 +- 1.40301       14       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.booking.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/8957695168833530224


For feedback, file a bug with component Speed>Bisection

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/15b5735c840000

Trying one more, wider bisect.

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/12c2132d840000

Not sure what happened with the previous bisect. Started another one with wider range.

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/12c2132d840000

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/1288d8d6440000

Manually going over the range in comment #3 (526672-526694), I couldn't find anything obvious. pinpoint is also failing.

However, looks like this has gone back down (after many ups and downs in between) to earlier levels (~27ms). So closing.

Pijat tradisional n refleksi

Pada tanggal Kam, 11 Jan 2018 7:20 PM, h… via monorail <
monorail+v2.3837952099@chromium.org> menulis: