New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 776749 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 774555
Owner: ----
Closed: Oct 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

8.1% regression in thread_times.key_mobile_sites_smooth at 508513:508614

Project Member Reported by pmeenan@chromium.org, Oct 20 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 20 2017

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

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


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

android-nexus6
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 20 2017


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

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : thread_times.key_mobile_sites_smooth
  Metric       : thread_total_fast_path_cpu_time_per_frame/http___www.boingboing.net

Revision             Result                   N
chromium@508512      14.3534 +- 1.06766       21      good
chromium@508614      14.3448 +- 0.821857      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...www.boingboing.net thread_times.key_mobile_sites_smooth

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

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


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Oct 23 2017

Mergedinto: 774555
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : sunxd
  Commit : 48493dc45de06867eec97e7944f56d511e3c4578
  Date   : Thu Oct 12 20:25:14 2017
  Subject: cc: make solid color picture layer tiling respect device scale factor

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : thread_times.key_mobile_sites_smooth
  Metric       : thread_total_fast_path_cpu_time_per_frame/http___www.boingboing.net
  Change       : 7.25% | 13.3123767613 -> 14.2772038747

Revision             Result                   N
chromium@508367      13.3124 +- 0.394159      6      good
chromium@508429      13.4414 +- 0.193596      6      good
chromium@508437      13.3728 +- 0.396764      6      good
chromium@508441      13.3507 +- 0.520008      6      good
chromium@508442      14.4323 +- 0.390852      6      bad       <--
chromium@508443      14.4372 +- 0.279228      6      bad
chromium@508445      14.4555 +- 0.254159      6      bad
chromium@508460      14.4181 +- 0.482489      6      bad
chromium@508491      14.3328 +- 0.29921       6      bad
chromium@508614      14.2772 +- 0.259773      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...www.boingboing.net thread_times.key_mobile_sites_smooth

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

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


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment