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

Issue 762185 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

7.1%-64.6% regression in thread_times.key_silk_cases at 498452:498950

Project Member Reported by briander...@chromium.org, Sep 5 2017

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=762185

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


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

android-nexus5X
android-nexus7v2
android-one
android-webview-nexus5X
android-webview-nexus6

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : thread_times.key_silk_cases
  Metric       : thread_renderer_main_cpu_time_per_frame/infinite_scrolling.html

Revision             Result                   N
chromium@498629      3.26441 +- 0.219639      14      good
chromium@498886      5.40262 +- 0.303594      14      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=infinite.scrolling.html thread_times.key_silk_cases

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

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


For feedback, file a bug with component Speed>Bisection
Re-running bisect.
Project Member

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


=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : thread_times.key_silk_cases
  Metric       : thread_renderer_compositor_cpu_time_per_frame/infinite_scrolling.html

Revision             Result                   N
chromium@498629      4.87153 +- 0.126768      14      good
chromium@498886      4.94976 +- 0.278383      14      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=infinite.scrolling.html thread_times.key_silk_cases

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

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


For feedback, file a bug with component Speed>Bisection
Status: WontFix (was: Untriaged)
Small regression, can't bisect.

Sign in to add a comment