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

Issue 737510 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Last visit > 30 days ago
Closed: Jan 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

106.9%-381.5% regression in v8.browsing_mobile at 477936:481403

Project Member Reported by ulan@google.com, Jun 28 2017

Issue description

See the link to graphs below.
 

Comment 2 by u...@chromium.org, Jun 28 2017

Status: Untriaged (was: Assigned)
Project Member

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


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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-total_avg/browse_chrome/browse_chrome_omnibox

Revision             Result                  N
chromium@481233      5.62592 +- 4.67618      15      good
chromium@481403      5.69444 +- 4.79796      16      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.chrome.omnibox v8.browsing_mobile

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

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


| 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!
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Jun 28 2017


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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-total_avg/browse_chrome/browse_chrome_omnibox


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.chrome.omnibox v8.browsing_mobile

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

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


| 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!

Comment 7 by u...@chromium.org, Jun 28 2017

Cc: -ulan@google.com
Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Jun 28 2017

Cc: hpayer@chromium.org
Owner: hpayer@chromium.org

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

Hi hpayer@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 : hpayer
  Commit : 0d2ed6c3287ec48ee06ec1b69287ed4bf0dd60d7
  Date   : Mon Jun 19 10:16:13 2017
  Subject: [heap] Allow a minimum semi-space size of 512K.

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-total_max/browse_chrome/browse_chrome_omnibox
  Change       : 93.75% | 24.4143333333 -> 47.3023333333

Revision                           Result                   N
chromium@477635                    24.4143 +- 13.2273       6      good
chromium@479441                    21.5607 +- 4.12646       6      good
chromium@480344                    18.9158 +- 5.18538       6      good
chromium@480795                    19.648 +- 7.70095        6      good
chromium@480810                    18.8547 +- 8.38369       6      good
chromium@480817                    16.9523 +- 5.83651       6      good
chromium@480821                    17.6895 +- 5.11148       6      good
chromium@480821,v8@8a32788f39      16.927 +- 5.86143        6      good
chromium@480821,v8@f626d5df7e      15.4978 +- 0.157882      6      good
chromium@480821,v8@bc717ae84b      18.3665 +- 8.86061       6      good
chromium@480821,v8@0d2ed6c328      51.9615 +- 7.44458       6      bad       <--
chromium@480821,v8@d6c9e534c8      51.1523 +- 9.94017       6      bad
chromium@480821,v8@2325ef535f      53.1008 +- 2.14625       6      bad
chromium@480822                    53.1362 +- 1.05059       6      bad
chromium@480823                    52.521 +- 2.21645        6      bad
chromium@480824                    50.6035 +- 9.62393       6      bad
chromium@480852                    53.0598 +- 1.04387       6      bad
chromium@480908                    53.4413 +- 0.945121      6      bad
chromium@481021                    52.4852 +- 3.96452       6      bad
chromium@481246                    47.3023 +- 0.614361      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.chrome.omnibox v8.browsing_mobile

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

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


| 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!
Project Member

Comment 9 by sheriffbot@chromium.org, Jul 11 2017

Labels: Hotlist-Google
Status: Archived (was: Untriaged)

Sign in to add a comment