New issue
Advanced search Search tips

Issue 661945 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 661064
Owner:
Closed: Nov 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.9% regression in memory.top_10_mobile at 428694:428709

Project Member Reported by primiano@chromium.org, Nov 3 2016

Issue description

The only v8 cl in range is
https://codereview.chromium.org/2453973004
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=661945

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgo__xtQoM


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

android-nexus5X
Cc: rmcilroy@chromium.org
Mergedinto: 661064
Status: Duplicate (was: Assigned)

===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : [compiler] Ship Ignition for all TurboFan code.
Author  : mstarzinger
Commit description:
  
This enables Ignition unconditionally for all code that is destined for
optimization with TurboFan. This ensures all optimization attempts will
go through the BytecodeGraphBuilder and that the AstGraphBuilder pipe is
dried out in practice.

patch from issue 2427953002 at patchset 120001 (http://crrev.com/2427953002#ps120001)

R=mvstanton@chromium.org,rmcilroy@chromium.org

Review-Url: https://codereview.chromium.org/2453973004
Cr-Commit-Position: refs/heads/master@{#40663}
Commit  : b4b436de6ad42e83d259418965a1a62c540a9fc7
Date    : Mon Oct 31 09:43:43 2016


===== TESTED REVISIONS =====
Revision                       Mean     Std Dev  N   Good?
chromium@428693                6129390  109941   12  good
chromium@428693,v8@b4b436de6a  6203791  111813   12  bad    <--
chromium@428693,v8@174da467ec  6274186  114451   8   bad
chromium@428694                6287696  131921   8   bad
chromium@428695                6275080  135398   8   bad
chromium@428697                6178879  93558.4  12  bad
chromium@428701                6258305  138297   12  bad
chromium@428709                6275761  123318   8   bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 661945

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_https_www_google_co_uk_hl_en_q_science
Relative Change: 3.04%
Score: 98.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/829
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997020600019959568


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6430573956956160

| 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 Tests>AutoBisect.  Thank you!

Sign in to add a comment