New issue
Advanced search Search tips

Issue 737495 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jul 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

7.3%-13.5% regression in v8.runtimestats.browsing_mobile at 481826:481898

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

Cc: mlippautz@chromium.org
Owner: mlippautz@chromium.org

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

Hi mlippautz@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 : Michael Lippautz
  Commit : 07b1113252bd487aa20d6459e03d125edf6d5e47
  Date   : Fri Jun 23 08:35:51 2017
  Subject: [heap] Move first-level on Scavenger to instance-based visitor

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-scavenger_avg/browse_chrome/browse_chrome_omnibox
  Change       : 5.95% | 6.70662208217 -> 7.10590522876

Revision                           Result                   N
chromium@481825                    6.70662 +- 0.774482      9       good
chromium@481847                    6.65473 +- 0.372571      9       good
chromium@481847,v8@e65aeada27      6.64425 +- 1.11384       14      good
chromium@481847,v8@1541f422a7      6.72545 +- 1.58119       14      good
chromium@481847,v8@07b1113252      7.0759 +- 0.371268       9       bad       <--
chromium@481847,v8@a7e622ba33      7.1292 +- 0.744532       14      bad
chromium@481848                    6.99872 +- 0.616312      14      bad
chromium@481849                    7.07291 +- 0.391077      6       bad
chromium@481850                    6.99262 +- 0.12426       6       bad
chromium@481853                    6.93836 +- 0.450376      9       bad
chromium@481858                    6.98233 +- 0.411803      9       bad
chromium@481868                    7.10591 +- 0.429456      9       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.runtimestats.browsing_mobile

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

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


| 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!
Cc: -mlippautz@chromium.org
Waiting a bit here since the regressions on the micro benchmarks have already been fixed.
Status: Assigned (was: Untriaged)
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Jun 29 2017

Cc: u...@chromium.org
 Issue 737492  has been merged into this issue.
Status: Fixed (was: Assigned)
Recovered.

Sign in to add a comment