New issue
Advanced search Search tips

Issue 661551 link

Starred by 2 users

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

1.2% regression in jetstream at 428678:428711

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

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=661551

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


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

chromium-rel-win7-dual
Mergedinto: 661064
Status: Duplicate (was: Untriaged)

===== 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@428677                179.875  0.834523  8  good
chromium@428686                179.375  0.744024  8  good
chromium@428690                179.875  0.991031  8  good
chromium@428692                180.125  0.64087   8  good
chromium@428693                179.875  0.834523  8  good
chromium@428693,v8@b4b436de6a  178.375  0.916125  8  bad    <--
chromium@428693,v8@174da467ec  178.125  0.64087   8  bad
chromium@428694                178.0    0.755929  8  bad
chromium@428711                177.4    0.547723  5  bad

Bisect job ran on: win_perf_bisect
Bug ID: 661551

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests jetstream
Test Metric: Score/Score
Relative Change: 1.66%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/7034
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997106302237672064


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

| 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