New issue
Advanced search Search tips

Issue 789448 link

Starred by 1 user
Status: Duplicate
Merged: issue 788488
Owner: ----
Closed: Nov 2017
Cc:
jgruber@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

54.8% regression in v8.browsing_mobile at 518400:518507

Project Member Reported by jgruber@chromium.org, Nov 29 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 29 2017 

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

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


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

android-nexus5X
Project Member

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


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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : total:500ms_window:renderer_eqt:v8_max/browse_shopping/browse_shopping_avito

Revision             Result                  N
chromium@518399      286.442 +- 195.703      21      good
chromium@518507      259.229 +- 161.66       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=browse.shopping.avito v8.browsing_mobile

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

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


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

Comment 6 by 42576172...@developer.gserviceaccount.com, Nov 30 2017

Mergedinto: 788488
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Mythri Alle
  Commit : 2d88095699f02011d0d0c7d21bf4f348ae453b20
  Date   : Wed Nov 22 11:48:27 2017
  Subject: Remove v8.browsing_desktop and v8.browsing_mobile benchmarks.

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : total:500ms_window:renderer_eqt:v8_max/browse_shopping/browse_shopping_avito
  Change       : 57.52% | 278.13401938 -> 438.122333333

Revision             Result                  N
chromium@518399      278.134 +- 100.763      6      good
chromium@518505      281.896 +- 85.0571      6      good
chromium@518558      285.153 +- 85.0252      6      good
chromium@518584      246.746 +- 70.6615      6      good
chromium@518597      256.124 +- 102.886      6      good
chromium@518604      268.508 +- 83.7797      6      good
chromium@518607      288.057 +- 124.064      6      good
chromium@518608      278.385 +- 58.2215      6      good
chromium@518609      439.055 +- 71.8432      6      bad       <--
chromium@518610      438.122 +- 45.4219      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.shopping.avito v8.browsing_mobile

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

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


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

Comment 7 by 42576172...@developer.gserviceaccount.com, Nov 30 2017 


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

Suspected Commit
  Author : Mythri Alle
  Commit : 2d88095699f02011d0d0c7d21bf4f348ae453b20
  Date   : Wed Nov 22 11:48:27 2017
  Subject: Remove v8.browsing_desktop and v8.browsing_mobile benchmarks.

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : total:500ms_window:renderer_eqt:v8_max/browse_shopping/browse_shopping_avito
  Change       : 55.66% | 287.939833333 -> 448.202

Revision             Result                  N
chromium@518399      287.94 +- 66.6061       6      good
chromium@518505      285.719 +- 83.2768      6      good
chromium@518558      288.04 +- 125.548       6      good
chromium@518584      247.544 +- 81.6437      6      good
chromium@518597      290.814 +- 120.49       6      good
chromium@518604      293.066 +- 97.4666      6      good
chromium@518607      258.518 +- 73.2048      6      good
chromium@518608      269.308 +- 83.3341      6      good
chromium@518609      444.931 +- 49.0445      6      bad       <--
chromium@518610      448.202 +- 49.9215      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.shopping.avito v8.browsing_mobile

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

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


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

Sign in to add a comment