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

Issue 759689 link

Starred by 1 user
Status: Fixed
Owner:
pfeldman@chromium.org
Closed: Dec 2017
Cc:
pfeldman@chromium.org
█ kraynov@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

33% regression in system_health.common_mobile at 496635:496661

Project Member Reported by kraynov@chromium.org, Aug 28 2017 
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=759689

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


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

android-webview-nexus6
Project Member

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


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

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : timeToFirstMeaningfulPaint_avg/load_news/load_news_nytimes

Revision             Result                  N
chromium@496634      511.2 +- 61.7132        21      good
chromium@496661      513.132 +- 82.0698      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=load.news.nytimes 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/8970000016124771840


For feedback, file a bug with component Speed>Bisection

Comment 6 by sullivan@chromium.org, Oct 9 2017 

Kicked off a few more bisects on the non-webview n6
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Oct 9 2017

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

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

Hi pfeldman@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 : Pavel Feldman
  Commit : 9ce7836fdec98fde42fc61347c4161077dbea0fc
  Date   : Wed Aug 23 07:07:21 2017
  Subject: DevTools: introduce lifecycle events reported over the page domain.

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : timeToFirstMeaningfulPaint_avg/load_tools/load_tools_docs
  Change       : 9.60% | 873.126714286 -> 930.596714286

Revision             Result                  N
chromium@496588      873.127 +- 186.818      14      good
chromium@496598      875.747 +- 187.896      14      good
chromium@496603      769.673 +- 211.484      9       good
chromium@496605      712.296 +- 55.6403      6       good
chromium@496606      725.289 +- 56.6513      6       good
chromium@496607      927.775 +- 158.314      14      bad       <--
chromium@496625      927.89 +- 215.032       21      bad
chromium@496661      930.597 +- 106.065      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=load.tools.docs 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/8966179883431932944


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

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


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

Suspected Commit
  Author : Pavel Feldman
  Commit : 9ce7836fdec98fde42fc61347c4161077dbea0fc
  Date   : Wed Aug 23 07:07:21 2017
  Subject: DevTools: introduce lifecycle events reported over the page domain.

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : timeToFirstMeaningfulPaint_avg/browse_news/browse_news_reddit
  Change       : 26.87% | 733.373666667 -> 930.460666667

Revision             Result                  N
chromium@496588      733.374 +- 74.4003      6      good
chromium@496598      740.91 +- 54.1773       6      good
chromium@496603      752.97 +- 88.7085       6      good
chromium@496605      750.046 +- 40.4726      6      good
chromium@496606      720.139 +- 59.554       6      good
chromium@496607      937.117 +- 65.8643      6      bad       <--
chromium@496625      932.279 +- 35.357       6      bad
chromium@496661      930.461 +- 71.2476      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=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/8966179886758731136


For feedback, file a bug with component Speed>Bisection
►

Sign in to add a comment