New issue
Advanced search Search tips

Issue 691049 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Feb 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.7% regression in thread_times.simple_mobile_sites at 449158:449195

Project Member Reported by majidvp@google.com, Feb 10 2017

Issue description

See the link to graphs below.
 

Comment 1 by majidvp@google.com, Feb 10 2017

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

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


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

android-one
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Feb 10 2017

Cc: jinsuk...@chromium.org
Owner: jinsuk...@chromium.org

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

Hi jinsukkim@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 : jinsukkim
  Commit : d95ac3f4aad80e2102fd8cf957dc2e265c0f02f7
  Date   : Thu Feb 09 01:57:19 2017
  Subject: Refactor ContentViewClient (4/6)

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : thread_times.simple_mobile_sites
  Metric       : thread_browser_cpu_time_per_frame/thread_browser_cpu_time_per_frame
  Change       : 2.53% | 4.26726596601 -> 4.37502712946

Revision             Result                    N
chromium@449157      4.26727 +- 0.036759       6      good
chromium@449176      4.22495 +- 0.149587       6      good
chromium@449181      4.2488 +- 0.0436424       6      good
chromium@449184      4.24454 +- 0.0292173      6      good
chromium@449185      4.24986 +- 0.0510687      6      good
chromium@449186      4.38201 +- 0.052505       6      bad       <--
chromium@449195      4.37503 +- 0.0376875      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 thread_times.simple_mobile_sites

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

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


| 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!
Cc: vmi...@chromium.org
Status: Assigned (was: Untriaged)
Status: Fixed (was: Assigned)
The CL was reverted.
Just curious, are you planning to re-land after addressing perf issues?
Yes
Labels: Performance-Responsiveness

Sign in to add a comment