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

Issue 759645 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

29.8% regression in system_health.common_mobile at 496951:497006

Project Member Reported by kraynov@chromium.org, Aug 28 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 28 2017

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

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


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

android-nexus7v2
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 28 2017


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

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : timeToFirstMeaningfulPaint_avg/load_search/load_search_ebay

Revision             Result                  N
chromium@496950      963.55 +- 299.512       21      good
chromium@497006      963.914 +- 185.845      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=load.search.ebay system_health.common_mobile

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

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


For feedback, file a bug with component Speed>Bisection
Kicked bisects on some other bots.

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : timeToFirstMeaningfulPaint_avg/browse_news/browse_news_reddit


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=browse.news.reddit system_health.common_mobile

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

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


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

Comment 8 by 42576172...@developer.gserviceaccount.com, Oct 10 2017

Cc: bcwh...@chromium.org
Owner: bcwh...@chromium.org
Status: Assigned (was: Untriaged)

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

Hi bcwhite@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 : Brian White
  Commit : 7662ff8cb53121cd4d8916007d430b36efd45895
  Date   : Thu Aug 24 00:03:13 2017
  Subject: Validate histograms before and after each task on Android.

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : timeToFirstContentfulPaint_avg/browse_news/browse_news_cnn
  Change       : 8.95% | 1445.23462222 -> 1574.56913333

Revision             Result                  N
chromium@496601      1445.23 +- 210.41       9       good
chromium@496862      1463.15 +- 252.843      14      good
chromium@496871      1433.62 +- 163.796      6       good
chromium@496875      1423.02 +- 158.802      6       good
chromium@496877      1472.13 +- 151.598      9       good
chromium@496878      1571.22 +- 259.869      14      bad       <--
chromium@496879      1572.45 +- 280.467      14      bad
chromium@496895      1573.56 +- 218.172      13      bad
chromium@496927      1565.35 +- 102.195      9       bad
chromium@496992      1588.6 +- 71.4101       6       bad
chromium@497122      1574.57 +- 108.716      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=browse.news.cnn system_health.common_mobile

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

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


For feedback, file a bug with component Speed>Bisection
Mergedinto: 758921
Status: Duplicate (was: Assigned)
WTF?  This was reverted some 6 weeks ago (as intended).
Just going through and clearing out old perf bugs, making sure the cause of each is known. Sorry for the noise.

Sign in to add a comment